ApiChats

List chat messages (deprecated)

GET
/chats

Deprecated — these endpoints will be removed on or after 5 January 2027.

Chats stores messages and nothing else: it does not generate a reply, it does not run your assistant, and no other part of the platform reads what you put here. The reply you store is one your own application already produced, so this is a database you have to authenticate to rather than a capability you gain.

Keep your messages in your own storage instead. To give a voice call the history of an earlier chat, return it as system context in your response to the assistant-request webhook, which already reaches you on every inbound call.

List chat messages for a contact, newest first. Use this for dashboards or manual inspection; use /chats/context when feeding history to an LLM or voice agent.

Authorization

BearerAuth
AuthorizationBearer <token>

API key authentication. Get your key from the dashboard.

In: header

Query Parameters

contact_id*string

External contact identifier (phone, session id, email, …)

channel?string

Filter by channel (whatsapp, web, sms, email, …)

agent_id?string

Filter by associated agent

Formatuuid
limit?integer

Maximum number of messages (max 500)

Default100
Rangevalue <= 500
offset?integer

Number of messages to skip

Default0

Response Body

application/json

application/json

curl -X GET "https://example.com/chats?contact_id=string"
{
  "messages": [
    {
      "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
      "agent_id": "2b1e3b65-2c04-4fa2-a2d7-467901e98978",
      "contact_id": "+31612345678",
      "channel": "whatsapp",
      "role": "user",
      "content": "string",
      "metadata": {
        "provider_message_id": "wamid.ABC",
        "attachments": []
      },
      "created_at": "2019-08-24T14:15:22Z"
    }
  ],
  "pagination": {
    "total": 42,
    "limit": 100,
    "offset": 0
  }
}
{
  "error": "Invalid API key",
  "message": "string"
}

Remove a lead DELETE

Remove a lead from a campaign.

Get conversation context for a contact (deprecated) GET

**Deprecated — these endpoints will be removed on or after 5 January 2027.** Chats stores messages and nothing else: it does not generate a reply, it does not run your assistant, and no other part of the platform reads what you put here. The reply you store is one your own application already produced, so this is a database you have to authenticate to rather than a capability you gain. Keep your messages in your own storage instead. To give a voice call the history of an earlier chat, return it as system context in your response to the assistant-request webhook, which already reaches you on every inbound call. Return the last N messages for a contact in chronological order (oldest → newest). The response contains two views: - `messages`: raw message rows ready to map into an LLM chat array. - `formatted`: a single string (`ROLE: content` per line) convenient to append to a voice agent's system prompt for cross-channel continuity.