not_found

HTTP 404 · The route or the resource does not exist for this account.

Endpoints: Any

When it happens

When	Message (as returned)	Fix (as returned)
No route matches the path (checked before the API key). Also when a path id has a character other than a letter, a digit or _.	No route for {METHOD} {path}.	See https://replyz.io/llms.txt for the API.
Inbox routes: the inbox does not exist, is deleted, belongs to another account, or the id is not an inbox id.	Inbox not found.	List your inboxes with GET /v1/inboxes.
GET /v1/account, POST /v1/inboxes: the account row is missing (should not happen with a valid key).	Account not found.	Sign up again with POST /v1/signup.
GET /v1/messages/{id}, POST /v1/messages/{id}/extract: the message does not exist for this account, belongs to a deleted inbox, or the id is not a message id.	Message not found.	Use a message id (msg_…) from a list or wait result.
GET /v1/messages/{id}/attachments/{att}: the attachment or message is not found for this account, an id has the wrong form, the message’s inbox was deleted, or the stored file is missing.	Attachment not found.	Use ids from GET /v1/messages/{id} (attachments[]).
GET /v1/threads/{id}: the thread does not exist for this account, belongs to a deleted inbox, or the id is not a thread id.	Thread not found.	Use a thread_id from a message.

What to do

• Check the id: it must come from this account and keep its prefix (ibx_, msg_, thr_, att_). Mail of a deleted inbox is gone from every route.
• For an unknown route, check the path against the API reference.

Not available yet

The route fix text points to the website’s llms.txt. The API’s own index is https://docs.replyz.io/llms.txt.

Example

{
  "type": "https://docs.replyz.io/errors/not_found",
  "code": "not_found",
  "status": 404,
  "message": "No route for GET /v1/nope.",
  "fix": "See https://replyz.io/llms.txt for the API.",
  "docs": "https://docs.replyz.io/errors/not_found.md"
}

All codes: Errors.