Try it | Mantys Eligibility API

Simulate the whole flow, one request at a time, with the cURL generated as you go.

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.

Insurer or TPA

ID typeIdentifier

Visit typeDoctor licence ID optional

EXTRA_ARGS FOR THIS COMBINATION

Bypass the referral requirement? optional Referral document URL optional Referring clinician optional Member present at the facility? optional

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://prod.api.mantys.org/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 Every scenario the API supports, including payer-specific identifiers, maternity and dental checks, the extras each payer reads, and Daman’s visit types.

Where these responses come from

The flow is simulated: polls advance on a keypress and nothing leaves your browser. The bodies are not. Every data_dump on this page is read out of a completed production check, captured read-only and published under samples with the patient's name, identifiers, birth date and documents replaced by placeholders. So the keys, the nesting, the empty strings and the fields that are missing rather than null are all exactly what your client will receive.

The envelope around it is generated, because it has to answer to the form above: task ids, timestamps and request_dump follow the request you built.

What this leaves out

Credentials. The generated cURL reads $MANTYS_API_KEY, $MANTYS_CLINIC_ID and $MANTYS_CLIENT_ID from your shell, so you can paste it into a terminal that already has them. Nothing is typed into this page. See Authentication.
Timing. Polls here advance on a keypress. A real check takes seconds to minutes, and the recommended loop is every 5 seconds with a timeout.
The outcomes that are not about the patient. backoff, tpa_not_configured and transport errors are on the errors page.