Build on Num
Two HTTP APIs, both bearer-key, JSON in and out. One issues eSIMs for you; the other tells you what happened to orders your customers paid for through a Num payment link.
Corporate API
Issue travel eSIMs programmatically from prepaid credit, or hand your traveller a checkout and take a margin. Sandbox keys today: free credit, demo eSIMs, identical behaviour to live.
Partner order API
Read-only. For partners selling through a Num payment link: has this order been paid, and has the eSIM been issued? Poll it, reconcile against it.
Quickstart
- Sign up at numesim.uk/business with your company email, then ask us to open your account.
- In the console, create a
numk_test_key and add sandbox credit. Both are instant and free. - Call the API. The example below prices Japan and places a sandbox order that returns a demo activation code.
curl https://numesim.uk/v1/catalog?country=JP \
-H "Authorization: Bearer numk_test_…"
curl -X POST https://numesim.uk/v1/orders \
-H "Authorization: Bearer numk_test_…" \
-H "Idempotency-Key: order-0001" \
-H "Content-Type: application/json" \
-d '{"planId":"…","country":"JP","funding":"credit"}'
Going live
Live keys, live credit and real eSIMs are enabled per account once pricing and settlement are agreed. Nothing in your integration changes except the key prefix. The corporate reference lists the steps.
Contact
Integration questions and account approval: [email protected]. Quote your company name and, for order issues, the order id and UTC timestamp.