MANTYS ELIGIBILITY API

Check insurance eligibility across UAE payers

Submit an eligibility check through the Mantys API and receive a structured result. Checks run asynchronously against your clinic's configured payer connections.

1

Describe the check

This is the same set of choices a receptionist makes in the product. Each one maps to a field in the request body.

SimulatedThe flow runs in your browser and never calls the API. The response bodies are real: each one is a completed production check with the patient details replaced.

EXTRA_ARGS FOR THIS COMBINATION

Nothing here reaches the API

The request above is never sent, and the polls advance on a keypress. The bodies that come back are real: each one is the answer a payer gave on a completed production check, with the patient details replaced.
Example API request
BASE=https://hrcm-api.themantys.com/v2/api-integration-v3curl -sS -X POST "$BASE/create-task" \  -H "x-api-key: Bearer $MANTYS_API_KEY" \  -H "X-Clinic-ID: $MANTYS_CLINIC_ID" \  -H "X-Client-ID: $MANTYS_CLIENT_ID" \  -H 'Content-Type: application/json' \  -d '{    "tpa_name": "TPA004",    "id_type": "EMIRATESID",    "id_value": "784-0000-0000000-0",    "visit_type": "OUTPATIENT",    "doctorId": "DOC-0000000"  }'

RULES IN PLAY

NAS and Neuron bypass the referral unless told not toWorth knowing

NAS Administration Services ticks the portal's exception checkbox by default, so the check is submitted with no referral attached. Send exception_case: false to have the portal's own referral list searched, and referral_document_url when you hold the letter yourself.

See the worked request
COMMON SCENARIOS
Don’t know the patient’s payer? Use BOTH to search across DHPO (eClaimLink) and Riayati, then across every payer your clinic has credentials for.
Common search scenarios (opens in a new tab)Every scenario the API supports, including payer-specific identifiers, maternity and dental checks, the extras each payer reads, and Daman’s visit types.