Chat Bridge API
Chat Bridge is the omnichannel messaging platform by Voices. Its public API lets you integrate the platform’s communication services into your own applications through an HTTP REST interface. All requests are authenticated with an App-Key and use JSON as the data exchange format.
Available channels
Automated phone calls with text-to-speech (TTS) or pre-recorded audio, outbound routes, audio upload, and webhook notifications.
Send text, media, interactive, and template messages; manage templates and accounts; and receive webhook notifications.
Coming soon
The following channels are part of the platform and will be added to this documentation soon:
SMS text messaging. Coming soon.
RCS rich messaging. Coming soon.
Email delivery. Coming soon.
Getting started
To use the API you need an App-Key, which you can request from the Chat Bridge team. The App-Key comes preconfigured with the account and channel it is enabled for, so you don’t need to specify them on each request.
Include it in the x-api-key header of every request:
A single App-Key enables one channel. If you need to operate both Blaster and WhatsApp, request one App-Key per channel.
Authentication
Every request requires the x-api-key header. The following scenarios produce
an authentication or authorization error. The Message column shows the literal
string returned by the API:
Rate limiting
If your App-Key has a configured limit, a 60-second window applies. When
exceeded, the API responds with status 429:
Error format
Every error follows the same structure:
Support
For questions or to report an issue, contact the Chat Bridge team and include
the errorCode shown in the error response.

