The API follows a pure REST contract: the HTTP status code is the success or error signal.Documentation Index
Fetch the complete documentation index at: https://docs.1to1ai.com/llms.txt
Use this file to discover all available pages before exploring further.
Response shape
{ code, message? }.
Status families
| HTTP | Meaning | Retry? |
|---|---|---|
2xx | Success — 200 read, 201 created, 202 accepted (async), 207 multi-status. | — |
4xx | Request error — auth, validation, or missing resource. | No, fix it first. |
429 | Rate limit exceeded. | Yes, after the Retry-After. |
5xx | Server error. | Yes, with backoff. |
Common codes
INVALID_REQUEST — 400
INVALID_REQUEST — 400
The body failed schema validation (missing field, wrong type, value out of
range). The
message indicates which field failed.CONVERSATION_NOT_FOUND — 404
CONVERSATION_NOT_FOUND — 404
The
conversation identifier (uuid, whatsapp_user_id, or phone) does
not resolve to any conversation in the business.WINDOW_CLOSED — 422
WINDOW_CLOSED — 422
The 24h window is closed: you cannot send text, media, or quick replies.
Send a template to reopen it.
RATE_LIMIT_EXCEEDED — 429
RATE_LIMIT_EXCEEDED — 429
You exceeded 60 requests per minute. Wait the seconds from the
Retry-After header. See Rate limits.SEND_FAILED — 502
SEND_FAILED — 502
Meta rejected the send. The message is persisted as
failed. The request
can be retried.FETCH_FAILED — 500
FETCH_FAILED — 500
Server error while reading data. Retryable with backoff.
Each endpoint documents in the API Reference the full set of codes it can
emit.