Terudo for developers
How a travel business puts Terudo's travel eSIMs in its own flow, with Elements, the partner API or an AI agent.
Terudo supplies travel data eSIMs to travel businesses (agencies, visa services, tour operators, travel apps), which offer them to their own travellers. Terudo never sells to travellers on its own: every sale belongs to a partner.
There are three ways to put an eSIM offer in your traveller's flow. Most partners start with Elements and add the API later.
| You want to | Use | Key |
|---|---|---|
| Show the right plan on a page you already have (booking confirmation, visa approval, trip page, customer account) | Elements: one script, five drop-in pieces | Publishable pk_… |
| Create orders from your back office, deliver eSIMs at your net price, follow usage, receive events | Partner API and webhooks | Secret sk_… |
| Let an AI assistant quote and sell, or let your coding agent integrate Terudo | AI tools: MCP servers, skills, CLI | None for the docs, sk_/pk_ for the partner MCP |
Two ways a sale is paid
Chosen on each order, never fixed per account.
- Commission (default). Terudo sells to the traveller, who pays the public price on Terudo's hosted checkout (
checkout_url). You earn a commission, paid monthly. Your client discount (0 to 15 %, default 5 %) comes out of your commission. This is what Elements do. - Net price. You buy the eSIM at your net price from your prepaid credit, it is delivered at once (or on a date), and you invoice your client yourself. API only, secret key only.
Net prices, commissions and credit are your business data. They never appear with a publishable key, in Elements or in any public page. Never show them to a traveller.
Keys
Keys are created in the partner portal (https://terudo.com/portal/developers/) once Terudo has opened the API for your account.
| Prefix | Where it lives | What it reaches |
|---|---|---|
sk_live_… |
Your server only | The whole partner API, real sales |
sk_test_… |
Your server only | The whole API in the sandbox: nothing is charged or billed |
pk_live_… |
Your web pages | Public prices, quotes, checks and a payment link on Terudo's checkout |
pk_test_… |
Your web pages | Same, sandbox: the pay page simulates the payment |
A publishable key can list the sites (origins) allowed to use it. With a list, browsers on other sites are refused, and a return_url coming from the page is kept only on those sites. Without a list, the key works from any page but no return address is taken from the page.
The public demo key pk_test_terudo_demo_public needs no account: real catalogue, prices, quotes and checks, payment links disabled. Use it to prototype.
Base URLs
- Partner API:
https://terudo.com/api/partner/v1 - Elements script:
https://terudo.com/elements/v1.js - Partner MCP server (your keys):
https://terudo.com/api/partner/v1/mcp/ - Docs MCP server (open, no key):
https://terudo.com/mcp/ - OpenAPI:
https://terudo.com/developers/openapi.json
Pages of this documentation
- Quickstart: an eSIM offer on your confirmation page in five minutes.
- Elements: every element, option, callback and style.
- Put Terudo in your flow: recipes per page type and framework.
- Partner API: authentication, quotes, orders, idempotency, errors.
- API reference: every route, generated from the live definition.
- Webhooks: events, payload, signature checks in several languages.
- Testing and going live: test keys, sandbox, checklist.
- AI tools: MCP servers, agent skills, CLI, llms.txt.
- CLI:
terudoon the command line.
Every page is plain Markdown at its .md address. All of them in one file: https://terudo.com/llms-full.txt