Try it | Mantys Eligibility API

Create a v4 check with a test ID, poll it through its 10-second life and read the answer, with the cURL for each call.

Create a check

POST /v4/eligibility-checks. Pick a test case, or edit the body field by field; the JSON and the cURL follow.

Test caseCopied from Eligible response structure. A single-payer answer whatever tpa_name says.tpa_name

identifiers, 1 to 5

AHD caller. Derivation applies only to AHD keys; every other key must send visit_type.AHD callers send admit type and medical service, and the visit type is derived from them.visit_type

Optional fields

namedobphonedoctorIddoctorNamepayerName

extra_args

Also send "mode": "test". v3 accepted it without saying so; v4 refuses any field it does not declare.

Nothing here reaches the API

The page answers for the API, and only for test IDs. Each answer is the one the API gives for that case; your own request is echoed back in request.

Request body

{  "tpa_name": "TPA002",  "identifiers": [    {      "id_type": "EMIRATESID",      "id_value": "990-01"    }  ],  "visit_type": "OUTPATIENT"}

CURL HOSTUAT (test IDs only)Productionhttps://uat.hrcm-api.themantys.com

Create, with cURL

HOST=https://uat.hrcm-api.themantys.comcurl -sS -X POST "$HOST/v4/eligibility-checks" \  -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": "TPA002",    "identifiers": [      {        "id_type": "EMIRATESID",        "id_value": "990-01"      }    ],    "visit_type": "OUTPATIENT"  }'

Where these answers come from

Nothing on this page is sent to the API. Every answer is the one the API gives for that test ID: the same status codes, the same error details, and the same finished body, row for row. Two parts follow what you did here, as they do on the API:

request in the result is your own request laid over the case's, with each ID masked to its last 4 characters.
Timing runs on your browser's clock. A test check finishes 10 seconds after the create, whenever you poll it.

The check id, the clinic in request.practice_id and the timestamps are placeholders. A real create returns a new id each time; use the one it gives you.

What this leaves out

Credentials. The cURL reads $MANTYS_API_KEY, $MANTYS_CLINIC_ID and $MANTYS_CLIENT_ID from your shell. Nothing is typed into this page. See Authentication.
Real IDs. An ID that does not start with 990- gets the unknown-test-case 400 here. The API would start a real check at the payer for it.
Payer rules. A test ID skips them, so tpa_name, id_type, visit_type and the doctor are not checked against the payer. A real ID can still get a 400 for them; see Error codes.
The rest of v4. This page covers creating a check and getting its result. Everything else is on the v4 overview.