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

Member present at the facility? optional

Nothing here reaches the API

Every response is generated in your browser. The shapes and status values are the real ones; the values are invented.

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"  }'

SPECIAL CASES

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.

Supported scenarios & special cases See all supported scenarios, including payer-specific identifiers, maternity checks, additional fields, Daman visit types, and other special cases.

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.