RESTful API endpoints
A small, boring, well-documented HTTP surface. Nine resources, JSON in and JSON out, idempotency on every write and error codes that say what to do next.
- Base URL
- api.textreach.online/v2
- Auth
- Bearer key
- Rate limit
- 600 req/s default
Build order
- 1
Provision a key
Create a sandbox key from the console, scope it to the routes you need and pull the OpenAPI file.
- 2
Send one request
Post to /v2/messages with a destination and a template reference. The response carries the route and an estimated accept time.
- 3
Read the receipt
Poll the message resource or subscribe to delivery events. Both carry the same state machine.
- 4
Promote to live
Swap the key, keep the code. Sandbox and production share one schema and one set of error codes.
What it gives you
The core send, lookup and schedule surface
- Idempotency keys on every write, so a retried request never sends twice
- Cursor pagination with stable ordering across the message and event collections
- Template rendering server side, with locale fallback and per-market character set handling
- Scheduled sends with a cancel window right up to submission
- Sandbox keys that mirror production behaviour, including simulated failure codes
- OpenAPI 3.1 description published alongside the reference and versioned with the API
Wire restful api endpoints into your stack
Sandbox keys are free and behave exactly like production, including the failure codes. Nothing to schedule and nobody to talk to first.