Making requests
Base URL, authentication headers, formats, pagination, errors and limits.
Base URL
Each Inbox has its own address. All endpoints live under /api/v1/:
https://your-stack.inbox.getchat.360dialog.io/api/v1/You find the address by opening the Inbox from the Hub. Every number has its own Inbox, on its own servers and database, so its data stays separate from every other Inbox.
All requests must use HTTPS.
Authentication
Every request carries a user token:
Authorization: Token <token>The channel API key (D360-Api-Key) is not supported. To create a user and get its token, see Authentication.
Formats
Send request bodies as JSON with Content-Type: application/json. Form-encoded and multipart bodies are also accepted; use multipart to upload files. Responses are JSON.
Pagination
List endpoints return pages:
{
"count": 276,
"next": "https://your-stack.inbox.getchat.360dialog.io/api/v1/messages/?wa_id=4915112345678&limit=20&offset=20",
"previous": null,
"results": []
}Use limit and offset to move through pages. For messages, page with before_time instead: new messages keep arriving while you read, which shifts offsets but not timestamps.
Status codes
200
Success
201
Created
202
Accepted — a message was queued; it is not delivered yet
400
Something is wrong with the request; the reason field says what
403
Not signed in, or your user has no permission for this chat
423
The message queue is full
452
The contact does not exist (on GET /messages/), or the timestamp is in the future (on /mark_as_received/)
453
The conversation window has closed; only a template can be sent
503
The message gateway could not be reached; retry after a few seconds
Before retrying a 503 on a send, read the chat's messages: a request that timed out may still have queued the message.
Limits
Each Inbox keeps up to 1.5 million messages. When it is full, the oldest messages are removed first
Search covers up to 1 million messages
Was this helpful?