Available APIs
Channels API
Send your users’ messages (text, image, audio, video, or document) to BluBash through an API channel and get the AI agent’s reply in the same call.
Campaigns API
Add contacts to an Ongoing Campaign, schedule sends per contact, cancel queued messages, and check delivery status.
Base URL
Authentication
Every request needs the workspace API Key in theX-API-Key header. Header names are case-insensitive: x-api-key also works.
Get the API Key
The BluBash interface does not have a screen to generate API keys. Request the workspace API Key from BluBash support. To use the Channels API, also ask for the API channel setup, which support handles.Idempotency
The Channels API accepts the optionalX-Idempotency-Key header. Send a unique value per operation so that a retry of the same request does not create duplicate messages.
Response codes
Best practices
- Always use the same identifier for the same contact. In the Channels API, the
contactIdentifier. In the Campaigns API, theidentifierorcontact_id. Different identifiers create duplicate contacts. - Handle errors by code.
4xxerrors need a fix;5xxerrors can be retried. - Retry with exponential backoff. Wait longer between attempts and cap the number of retries.
- Validate in a test setup first. Use a test channel and a test campaign before pointing production traffic.
- Store the returned IDs. Keep
contactId,conversationId, andmessageIdto trace service and delivery.
How the API connects to the rest of BluBash
- Contacts created through the API appear in Contacts, with the tags and additional fields sent in the payload.
- API channel conversations are handled by the AI agent configured for the channel. See What are AI agents →.
- Contacts added through the API to an Ongoing Campaign appear with the API source in the campaign details. See Manage campaigns →.