Reach
Reach for developers
The Reach application interface, the versioned Reach API and signed webhooks: send, read, poll and react to client messages from your own systems.
The application interface
Every operation is an authenticated call to your STRAX installation, so your systems never talk to a messaging provider directly.
Send
Queue a message to a client on a named channel, or on the identity they used last.
Contact upsert
Create or update a client with their identities on every channel in one call.
Contact lookup
Find a client by your own reference, by id or by a channel address.
Conversations
List a client's conversations with the latest message of each.
Messages
Read or poll messages with a cursor, and check the status of one send.
Link codes
Issue a code and the links that let a client connect each channel.
One versioned API for your applications
Install the Reach API package and the application interface becomes Reach API v1 on the STRAX API gateway: clear routes for messages, contacts, conversations, identities and callbacks under one base path, with the contact or conversation named in the address.
Each application gets its own key with only the access it needs, whether reading, writing, sending or managing callbacks, and its own rate limit and quotas. Calls are counted per route, refused calls are recorded, and one OpenAPI document describes the whole API for your developers.
The API can answer under your installation address or on a hostname of its own. It needs the API gateway in your STRAX licence; without it, your systems use the interface directly as before.
Signed webhooks
Register a callback address and Reach posts an event when a message is received, sent or fails, with the message and the client in the body. Each call carries the event name and a token you choose, so your application can verify it.
Missed a call while your application was down? Poll the messages endpoint with the last cursor you saw and Reach returns everything that happened since.
Product names and logos of the supported services are trademarks of their respective owners and are used only to identify those services. Brand marks from Simple Icons (CC0); glyphs from Lucide (ISC).
See it on your own systems.
A demo takes an hour, on your data landscape rather than ours.