A global roaming API
where coverage is a field
Roaming is not a thing you buy on top. It is a property of the profile you already hold: queryable, settable, and reported per country rather than as one line at the end of the month.
Sandbox profiles are simulated and cost nothing. No card, no commitment.
True of every capability
- One call switches it on. No form, no approval step.
- One key covers everything. The same credentials across the platform.
- One invoice carries all of it. Every capability on a single bill.
- The sandbox works first. Build against simulated profiles from minute one.
- One click switches it off. Billing stops the moment you do.
Set the footprint. The profile carries it.
Five choices. One call. Every one of them is a field you can change afterwards.FOOTPRINT
OUTSIDE IT
NETWORKS
STEERING
REPORTING
esim_7Kd2xQA network in Portugal# The footprint, as one call
PATCH /v1/esim/esim_7Kd2xQ { "footprint": "europe", "outside": "block", "networks": "any", "steering": "cost", "report_by": "country" }
CROSSING A BORDER
What happens is what you said should happen.
A device moves. Nothing about your integration does.
The device attaches
Inside the footprint it connects. At the edge of it, what you set is what is attempted.
You are told
A webhook carries the profile, the country and the network it attached to.
Usage is attributed
Metered against the same allowance, reported per country or per network.
It is on the same invoice
Not a separate roaming bill arriving weeks later from somebody else.
The footprint is a field. Widening it for one device is a call, not a contract change.
WHO IT IS FOR
For products whose customers do not stay still
The usual roaming failure is not coverage. It is finding out, a month later, that a device spent a fortnight on an expensive network nobody chose.
Coverage you set rather than discover. Move a simulated profile across a border today, at no cost.
WHAT YOU GET
What switching it on actually does
Four things the founder has stated. Everything else on this page is drafting.
- What it does
- Switch it on and SIMs and eSIM profiles attach to networks abroad, within the countries the customer permits. Off means home country only.
- What it replaces
- Without it, you take whatever your supplier's agreements give you, everywhere, and find out where the device landed from the bill.
- How it is metered
- Metered in gigabytes, at a rate that differs by country and by network, plus the monthly fee on live activation. Nothing in the sandbox.
SESSION LIFECYCLE
Every state is queryable, and every transition fires a webhook.
TWO WAYS TO BUILD
Choose your pathway. Same platform either way.
Neither route is faster than the other. They differ in what arrives afterwards.
Your screens, your way
Footprint, attachment and per-country usage as endpoints, so where a device is allowed to go is part of your provisioning rather than a spreadsheet somebody maintains.
# Widen the footprint for one profile curl -X PATCH https://api.telyne.com/v1/esim/esim_7Kd2xQ \ -H "Authorization: Bearer sk_live_4a11" \ -d '{ "footprint":"global", "outside":"allow_alert" }'
# 200 OK { "id": "esim_7Kd2xQ", "footprint": "global", "attached": { "country": "PT" } }
Coverage that answers questions.Ask where a profile can go and where it has been, and get an answer from the platform rather than from a document written last year.
Our screens, inside your app
The coverage screens already built and themed to your brand: where a plan works, where a device is, what it used there, so your customers can answer their own questions.
Nobody reads a coverage map.They ask whether it works where they are going. The screens answer that question with the same data the API returns.
undefined undefined
WORKS WITH
Switch on the next one the same way
Nothing new to sign and nothing new to integrate. The same call with a different noun.
QUESTIONS
Roaming on Telyne
Is roaming a separate product I buy?
No. It is a property of the profile you already hold, set as a field and changed with one call. There is no separate agreement, no separate key and no separate invoice.
Can I control which networks a device uses?
You express the intent on the profile: the footprint it may attach within, and what should happen at the edge of it. The platform reports what actually happened, per country. How far a given network honours a preference is returned by the API rather than promised on this page.
How is roaming usage reported?
Against the same allowance the profile already has, attributed to where it was used, and on the same invoice rather than arriving separately weeks later.
Can I change the footprint after a device has shipped?
Yes. It is a PATCH on the profile and applies to the live session. Widening it for one device does not require changing anything for the rest.
How do I know where a profile can go?
Ask the API. The footprint is a field you set and read back, and where a profile may attach is queryable rather than published as a list that goes stale, so you can check before you provision rather than after.
Set a footprint before a device crosses a border
No approval step and nothing to sign. The sandbox is open now, and production access opens in the order requests arrive.
One email at launch. Nothing else, and unsubscribe in one click.
We send a link to confirm the address. Unconfirmed addresses are deleted after 30 days.
Complex requirement or an existing estate to move? Talk to us.