api.textreach.online

Three ways in

Most teams start with the REST surface, add a connector once operations wants to send from the CRM, then wire webhooks when the volume gets interesting. You can do them in any order.

Modules
3
Native connectors
8
SDK languages
5

The connector catalogue

Each connector is maintained by us and versioned against the API, so a schema change on either side does not become your on-call problem. Anything in-house speaks to the same generic outbound shape.

generic outbound connector

POST https://api.textreach.online/v2/messages
{
  "sender_id": "LUXPLAY",
  "to": "+35679xxxxxx",
  "template": "deposit_bonus_v3",
  "vars": { "amount": "50", "expiry": "22:00" },
  "external_ref": "crm:contact:88431"
}
  • Fernstack CRMPlayer CRM
  • HeliodeskSupport desk
  • CorevaultWarehouse
  • PipetreeAutomation
  • NordwavePlayer CRM
  • Quanta CDPCustomer data
  • SignalboxAnalytics
  • OrbitpayPayments

Running something that is not on this list? Tell us what it is - the generic connector covers most of them, and we build the ones that come up twice.

Every module runs against sandbox keys first, with simulated networks and forced failure codes, so you can prove the integration before a single real message is billed.

Developer hub

Pick the module you need first

The three surfaces share one schema and one set of error codes, so work you do against any of them carries into the others.