Join the waiting listJoin
Products
Company
About TelyneWho operates the platform. White labelSell under your own brand. Who it is forSix kinds of business.
Join the waiting list Sign in Explore the platform
Home/Capabilities/Developer platform/Webhooks

Telecom webhooks
you do not have to poll for

Everything asynchronous arrives as a webhook: signed so you can verify it came from us, retried with backoff when your endpoint is not there, and replayable when it was down for longer than that.

Start in the sandbox See how it works

Sandbox profiles are simulated and cost nothing. No card, no commitment.

Join the waiting list for production access

Point it somewhere. We deliver.

Five choices. One endpoint. Nothing here requires you to poll.

ENDPOINT

Your HTTPS URL

EVENTS

All A selected list

SIGNING

Signed

RETRIES

With backoff None

REPLAY

Available
Your endpointYour URL, your events, your verification
All eventssigned · retried
WEBHOOK IDwhk_6Tp1yE
LAST DELIVERY200, 0.4s ago

# The endpoint, as one call
POST /v1/webhooks  { "url": "https://you/hooks", "events": "all", "signing": true, "retries": "backoff", "replay": true }

WHEN YOU ARE DOWN

Delivery is our problem, not your uptime.

What happens between an event occurring and your system knowing about it.

FIRE

The event occurs

A profile activates, a threshold is crossed, a rule fires. Anything asynchronous.

POST

We deliver it, signed

So your handler can verify it came from us before it acts on it.

RETRY

If you are not there, we back off

Retried with backoff rather than dropped, and rather than hammering an endpoint that is struggling.

REPLAY

If you were down longer, replay it

Events are replayable, so an outage is a gap you can close rather than data you lost.

Nothing here asks you to poll. Polling is the failure mode webhooks exist to remove.

WHO IT IS FOR

For systems that must know when something changed

The alternative is polling, which is either too slow to be useful or too frequent to be affordable, and is wrong in both directions at once.

Event-driven backendsYour existing queue, fed by our events, in the shape you already handle.
Billing and reconciliationThreshold and lifecycle events as they happen rather than at month end.
Fleet operationsA device changing state is a message, not something to discover on a dashboard.
Anyone polling todayBecause there was no other way to find out.
No pollingDelivered, not fetched
No unsigned payloadsVerify before acting
No silent dropsRetried with backoff
No lost outageReplayable

You should not have to ask repeatedly. Point a simulated webhook at your endpoint today, at no cost.

Start in the sandbox Join the waiting list

WHAT YOU GET

Delivery that survives your endpoint having a bad day

What was sent, when, what came back and what is queued all come from the API.

THE CAPABILITY
Coverage
Everything asynchronous. If it happens without you asking, it arrives as an event.
Signing
Every payload signed, so a handler can verify origin before it acts.
Retries
Backoff rather than immediate repetition, so a struggling endpoint is not made worse.
Replay
Events can be replayed, so an outage is a gap to close rather than data that is gone.
Envelope
One envelope for every capability, so a second integration is not a second parser.
BUILDING ON IT
Keys
The same prefixed bearer tokens configure the endpoint. Test and live deliver separately.
Retries
Configuring an endpoint takes an idempotency key, so a retried setup call does not register a duplicate.
Errors
One shape everywhere: a type, a code, a message, the parameter at fault and a link. Never a bare 500 with a stack trace.
Reference
One published OpenAPI specification. The server validates against it, the SDKs are generated from it and the sandbox mocks from it.

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.

EventsWhat arrives in the envelope. LogsWhat was sent and what came back. REST APIThe other half of the same platform.

QUESTIONS

Webhooks on Telyne

What is delivered as a webhook?

Everything asynchronous. If something happens without you having asked for it in that moment (an activation, a threshold, a state change), it arrives as an event rather than waiting to be polled for.

How do I know a payload came from you?

Every payload is signed. Your handler verifies the signature before acting on it, which is why an endpoint can be public without being trusting.

What happens if my endpoint is down?

Delivery is retried with backoff rather than dropped or repeated immediately. If you were down longer than the retries cover, events are replayable so the gap can be closed.

Is the payload shape different per capability?

No. One envelope for every capability, so handling a second capability's events is not a second parser.

Do I still need to poll for anything?

No. Polling is the failure mode webhooks exist to remove: it is either too slow to be useful or too frequent to be affordable, and usually both at once.

Join

Point an endpoint somewhere before there is traffic

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.