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.

Join the waiting list for production access

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

Europe Americas Global

OUTSIDE IT

Block Allow and alert

NETWORKS

Any available Preferred list

STEERING

Cheapest first Strongest first

REPORTING

Per country Per network
Your footprintYour rules, your preferences, your reporting
Europeblock outside · cheapest first
PROFILEesim_7Kd2xQ
CURRENTLY ONA 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.

MOVE

The device attaches

Inside the footprint it connects. At the edge of it, what you set is what is attempted.

0s

You are told

A webhook carries the profile, the country and the network it attached to.

USE

Usage is attributed

Metered against the same allowance, reported per country or per network.

BILL

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.

Travel and mobilityCustomers who cross borders as a matter of course, on terms you set before they go.
Vehicles and logisticsAssets that move between markets without anyone provisioning them again.
Cross-border operationsOne footprint over several markets instead of one agreement per market.
Anyone burned beforeSet what happens outside the footprint, and it happens.
No separate productIt is a field on the profile
No per-country dealOne footprint, many markets
No surprise networkSteering is your choice
No second invoiceRated on the same bill

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.

THE CAPABILITY
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.
WHAT IT COSTS
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.

Reattach
In footprintAttachedCarryingOutsideDetached

TWO WAYS TO BUILD

Choose your pathway. Same platform either way.

Neither route is faster than the other. They differ in what arrives afterwards.

Telyne roaming API one field, one profile
APISDK
API

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.

One PATCHto widen a footprint Any languagethat speaks HTTP
# 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.

Simulated profiles, no card, no commitment. Start in the sandbox
SDK

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.

Swift · KotlinReact Native · Flutter

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.

Simulated profiles, no card, no commitment. Start in the sandbox

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.

Join

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.