Developer hub
Everything you need after the reference: clients, tooling, three worked guides, and a written record of what changed and when.
- SDK languages
- 5
- Spec
- OpenAPI 3.1
- Replay window
- 30 days
SDKs
Maintained clients for Node, Python, PHP, Go and Java, versioned against the API and published on the usual registries.
OpenAPI description
The full 3.1 description, published with each release so you can generate a client in whatever language you actually use.
Sandbox console
Simulated networks, forced failure codes and a live event tail, so edge cases can be reproduced on demand.
Postman collection
Every endpoint with example bodies and environment variables already wired for sandbox and production.
Status and incidents
Per-region gateway status, historical uptime and a written post-incident note for anything that lasted more than five minutes.
Changelog
Additive changes shipped weekly, breaking changes never inside a major version, deprecations announced twelve months ahead.
Guides
Three things worth reading before launch
Written by the integration engineers who answer the tickets, and kept in step with the API rather than left to rot.
- 01Send your first message in ten minutesProvision a key, register a sender, post one request and read the receipt that comes back.8 min read
- 02Reading delivery receipts and retry behaviourWhat each DLR state means, when the gateway retries, and how to make your webhook idempotent.11 min read
- 03Sender ID registration for regulated marketsHow alphanumeric sender registration works per network, what it costs in time, and what blocks it.9 min read
Changelog
What changed, and when
Additive changes ship weekly. Breaking changes never land inside a major version, and deprecations are announced twelve months ahead.
- added
Consent write-back now carries the originating channel, so an opt-out from a web form and one from a STOP reply are distinguishable.
- added
Per-key burst allowance is configurable from the console and from GET /v2/limits, without a support ticket.
- improved
Route selection for Nordic networks now prefers the lower-latency bind during local evening peak.
- added
Event replay window extended from seven to thirty days across all plans.
- fixed
Scheduled sends cancelled inside the final second returned 204 while still submitting. They now return 409 and do not send.
Who answers in here
Elias Fenech
Elias Fenech runs integration engineering out of the Malta office and has spent fifteen years on the carrier side of gaming traffic. The community threads are answered by the same four people who write the routing rules, which is why the answers tend to be specific.
Open a ticket insteadShip the integration this sprint
Pull the OpenAPI file, generate a client, run it against sandbox. The quickstart takes about ten minutes end to end.