STRAX Reach · Web and portal
One versioned API for every application that talks to your clients
Your billing system sends payment reminders, your CRM keeps client records current and your app reads the conversation history. The Reach API gives each of them one address, their own key and exactly the access they need.
- Clean, versioned routes
- A key per application
- OpenAPI contract
Reach, published as a real API
Reach Core already answers applications through its workflows. This package puts them behind the STRAX API gateway as Reach API v1: messages, contacts, conversations, identities and callbacks under one base path, with routes such as the contact by its identifier or the messages in a conversation.
Every application gets its own key with only the scopes it needs: read, write, send or administer callbacks. Each key can carry its own per-minute limit, daily and monthly quotas and a validity window, and it can be suspended in one step. Keys issued for the API reach Reach only through it.
The gateway answers every call with a request reference and standard error responses, keeps per-route metrics, records refused calls in the audit trail and produces the OpenAPI document your developers build against. The API can answer under your installation address or on a hostname of its own, and a later version can run beside it while applications move across.
Where it helps
Billing and collections
The billing system sends payment reminders and reads the replies with a key that can send and read, nothing more.
CRM synchronisation
The CRM creates and updates clients and their channel identities, and links them with one-time codes.
Your own portal or app
The portal shows a client their conversation history with a read-only key.
What you need
-
Reach Core
Its application workflows answer every route of the API.
-
The API gateway
The api.gateway capability of your STRAX licence.
-
HTTPS
The API refuses plain HTTP calls, so serve it over HTTPS or on a hostname with a certificate.
Good to know
The API installs as a draft, so nothing is reachable until you publish it. Removing a callback uses the register route with a remove flag rather than a separate delete route.
Questions
Do our existing integrations stop working?
No. Applications that already call the Reach workflows keep working; the API is an additional, managed way in.
How do applications authenticate?
Each sends its own key, subscribed to the API with the scopes it needs. Your administrator can switch the API to tokens from your identity provider as well.
Can one application be limited more than another?
Every key carries its own per-minute limit and daily and monthly quotas, so a busy batch job can be held tighter than an interactive portal.
Where do developers find the contract?
The OpenAPI document is downloaded from the API in the console, or published alongside it.
Read more
-
The whole Reach family →
Reach Core and every channel package, with what each one needs.
Add Reach API to Reach
Tell us which channels your clients use and we will plan the rollout with your team.
Premium Requires STRAX Reach - Core, which is licensed.
About this listing
| Version | 1.0.0 |
| Author | STRAX |
| Category | Communication |
| Published | 2026-09-26 |
What's inside
| Api product | 1 |
Free listing
Install it from Feature Marketplace inside STRAX
It builds on STRAX Reach - Core, a premium package. Ask us for a quote to license it first.
Open Feature Marketplace
In your STRAX installation, open Feature Marketplace from the navigation.
Find "STRAX Reach - API"
Search or browse to this listing and review the contents disclosure; every package shows what it contains before anything runs.
Install
Choose Install, or "Customise with AI" to adapt the package to your environment first. No licence is needed for free listings.
OpenAPI is a trademark of its owner, named here only to identify the service this package connects to.
See it on your own systems.
A demo takes an hour, on your data landscape rather than ours.