EDME-GO API documentation
One normalised travel protection API across the insurer stack. Read the reference, then run the same calls for free in the Integration Studio — no signup, no personal data, no production systems.
Start here
The public sandbox is open to everyone. A short-lived anonymous session is created for you automatically on first call and lasts 60 minutes. Fair-use limits apply: 30 requests per 10 minutes.
First call
curl -X POST https://www.edmetravel.com/api/sandbox/plans/search \
-H "Content-Type: application/json" \
-c sandbox-cookies.txt \
-d '{
"trip": { "origin_country": "IN", "destination_country": "AE", "start_date": "2026-11-04", "end_date": "2026-11-14" },
"travellers": [{ "age": 34 }]
}'Keep the session cookie between calls — policy references you create are readable only inside the session that created them.
The policy lifecycle
- 1Reference
Search plans
Trip and traveller ages in, normalised EDME-GO plan tiers out.
- 2Reference
Issue policy
Issue against a plan and receive an EDME policy reference and documents.
- 3Reference
Read status
Poll the lifecycle state of an issued policy at any time.
- 4Reference
Modify
Apply pre-approved correction scenarios such as date changes.
- 5Reference
Cancel
Cancel with a structured reason and read the resulting state.
What the sandbox will never do
- Accept traveller personal data. Identity is generated by EDME-GO under example.com.
- Touch production policies, insurer systems or live money.
- Return insurer-specific identifiers, plan naming or internal error text.
Sections: Overview · Access & limits · Search plans · Issue policy · Policy status · Modify policy · Cancel policy · Errors.
Ready to move past the sandbox?
We will map the same operations to your booking flow, agree servicing ownership and sequence go-live with your team.