Mobile data with
an allowance you can move
Set a limit, raise it at lunchtime, drop it back on Friday. The allowance is a value on the profile rather than a plan you reissue, and changing it does not reissue anything.
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 allowance. Change it whenever.
Five choices, none of them permanent. Every one is a field you can PATCH afterwards.REGION
ALLOWANCE
SPEED
PERIOD
AT THE CAP
plan_3Rm9tW6.4 GB of 20 GB# The allowance, as one call
POST /v1/data-plans { "region": "europe", "limit_gb": 20, "network": "5g", "period": "month", "on_limit": "throttle" }
CHANGING IT
Raising a cap is a PATCH, not a migration.
What it takes to move an allowance on a profile that is already carrying traffic.
Send the new value
One field on the plan. No new plan, no new profile, no reissue.
It applies live
The device keeps its session. Nothing reconnects and nothing drops.
Metering follows
The counter keeps its history and measures against the new ceiling.
Billed as used
You are rated on the megabytes, not on the size of the allowance.
The same call lowers it. An allowance is a number, not a contract.
WHO IT IS FOR
For products where usage is lumpy
If your customers use nothing for three weeks and everything in the fourth, a fixed monthly plan is the wrong shape and you end up buying for the peak.
Nothing to renegotiate. Move an allowance against a simulated plan today, at no cost.
WHAT YOU GET
An allowance that is a value, not a contract
Limits, periods and what happens at the ceiling are all fields, and all of them come back from the API rather than from this page.
- Allowances
- A ceiling in megabytes, or none, on a calendar month or a rolling window.
- At the cap
- Throttle, suspend, or notify and keep going, set per plan, changed per call.
- Metering
- Per megabyte, recorded as it happens, with the period's running total queryable.
- Changes
- PATCH the allowance live. The session survives and the counter keeps its history.
- Events
- Webhooks at every threshold you set, at the cap, and on every change to the plan.
- Keys
- Test and live keys are prefixed, so the two can never be confused in a log or a commit.
- Retries
- Every call that changes something takes an idempotency key. Retry without double-raising.
- Errors
- One error shape everywhere, each carrying a link to the page that explains it.
- Reference
- A published OpenAPI spec. The server validates against it and the SDKs are generated from it.
PLAN 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
Plans, counters and thresholds as endpoints, in whatever language you already write. Every number this page describes is a field you can read.
# Raise the cap, mid-period curl -X PATCH https://api.telyne.com/v1/data-plans/plan_3Rm9tW \ -H "Authorization: Bearer sk_live_4a11" \ -d '{ "limit_gb": 40 }'
# 200 OK { "id": "plan_3Rm9tW", "limit_gb": 40, "used_mb": 6553, "period": "month" }
The counter is not a summary.Usage is queryable at the same resolution it is billed at, so your invoice and your dashboard cannot disagree.
Our screens, inside your app
The allowance screens already built and themed to your brand: the meter, the threshold warning, the change-my-plan flow. You are not designing a usage dashboard from scratch.
The screens read the same fields you would.Nothing is computed in the client, so what a customer sees is what the API returned.
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
Mobile data on Telyne
Can I change an allowance while the device is connected?
Yes. The allowance is a field on the plan, so a PATCH applies to the live session. Nothing reconnects, the device does not notice, and the period's counter keeps its history rather than starting again.
What happens when a profile reaches its cap?
Whatever you set: throttle to a slower speed, suspend the session, or notify and keep going. It is a field on the plan and can be changed at any time, including after the cap has already been reached.
Am I billed for the allowance or for what is used?
For what is used, metered per megabyte as it happens. A twenty gigabyte ceiling on a profile that used six is rated at six. The ceiling is a control, not a purchase.
Is this a different product from eSIM?
No. It is the same connection seen from a different angle: the profile is issued by eSIM and the allowance sits on it. One account, one key, one invoice, and moving between them costs nothing.
Can different customers have different ceilings?
Yes. Each plan carries its own, set at creation or changed later, and they are managed from one account. Nothing about the arrangement has to be uniform.
Set an allowance, and move it before the month ends
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.