SIM lifecycle management
as verbs, not as tickets
Suspend, resume and retire are things you do to a profile you already hold. Each is one call, each fires a webhook, and none of them needs anybody's permission.
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.
Choose the verb. We apply it.
Five actions. One endpoint each. Nothing here opens a ticket.ACTION
APPLIES TO
WHEN
BILLING
REVERSIBLE
esim_7Kd2xQActive, 41 days# The verb, as one call
POST /v1/esim/esim_7Kd2xQ/suspend { "action": "suspend", "scope": "profile", "when": "now", "billing": "stop", "reversible": true }
THE WHOLE LIFE
Issued to retired, and every step reversible until the last.
What a profile can do at each point, and what it costs you while it sits there.
It exists
Addressable and queryable before it has ever carried a byte.
It carries traffic
Metered as it happens, against whatever allowance it holds.
It is suspended
One call. Billing stops with it, the history stays, and resuming is one call back.
It is retired
The one step that does not reverse. Usage stays queryable so the period can still be reconciled.
A profile sitting suspended costs nothing. That is the point of having the verb.
WHO IT IS FOR
For estates where devices come and go
Hardware is returned, customers churn, seasons end and units fail. If pausing a connection means an email to a supplier, none of that is manageable at scale.
Pausing should be easier than forgetting. Suspend and resume a simulated profile today, at no cost.
WHAT YOU GET
Every transition is a call, and every one fires an event
State, history and what each verb costs all come from the API rather than from an account manager.
- Suspend
- Stops the session and stops billing with it. The profile keeps its id, its allowance and its history.
- Resume
- The same profile back, not a reissued one. Counters continue rather than restarting.
- Retire
- The one irreversible verb. Billing stops and usage stays queryable for reconciliation.
- Events
- Webhooks on suspended, resumed, transferred and retired, each carrying the previous state.
- Keys
- Test and live keys are prefixed, so a retirement cannot be issued against the wrong environment.
- Retries
- Every verb takes an idempotency key. Retrying a suspend does not suspend something else.
- Errors
- One shape everywhere: a type, a code, a message, the parameter at fault and a link to the page that explains it.
- Reference
- One published OpenAPI specification. The server validates against it, the SDKs are generated from it and the sandbox mocks from it.
PROFILE 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
Each verb as an endpoint, so suspending on return and resuming on dispatch are lines in the system you already run rather than steps somebody remembers.
# Suspend on return curl https://api.telyne.com/v1/esim/esim_7Kd2xQ/suspend \ -H "Authorization: Bearer sk_live_4a11" \ -H "Idempotency-Key: ret_2290"
# 200 OK { "id": "esim_7Kd2xQ", "state": "suspended", "billing": "stopped", "previous": "active" }
The history survives the verb.A suspended profile keeps its counters and its record, so resuming continues rather than starting again and the period still reconciles.
Our screens, inside your app
The state screens already built and themed to your brand: the current state, the history, the pause and resume controls, for when your customers manage their own devices.
A pause button people can find.Most idle spend exists because stopping was harder than continuing. The screens make it one tap.
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
SIM lifecycle on Telyne
Does suspending a profile stop the billing?
Yes, with it. A suspended profile costs nothing while it sits there, which is the reason to have the verb at all. Resuming starts it again from the same profile.
Is resuming the same profile or a new one?
The same one. It keeps its id, its allowance and its counters, so a resumed profile continues rather than starting again and the period still reconciles.
Which of these can I undo?
All of them except retire. Retirement is deliberately irreversible; everything before it is a call back the other way.
Can I act on a whole fleet at once?
Yes. Each verb takes a scope, so it applies to one profile or to a group, and a single device inside a group can still be addressed by its own id.
What happens to usage history when a profile is retired?
It stays queryable. Billing stops when the profile does, but the record of what it used remains so the period it was live in can still be reconciled.
Take control of a profile you have not issued yet
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.