Overview
Browse every error code the BeeL. API can return, organised by domain. Every error response includes a stable type URI pointing to its page here.
How error responses work
Every API error response follows the RFC 9457 Problem Details for HTTP APIs contract. The type field is a URI that points to a stable documentation page right here — copy it from any error response into your browser to jump straight to the relevant entry.
438 codes across 15 domains.
Start here
Handling errors
How to parse responses, branch on the code, and deep-link to docs from the type URI. Read this first.
All codes in one view
Flat alphabetical table. Useful as a cheat sheet or to copy into your codebase as constants.
Browse by category
Get the email indicators of several entities (deprecated) GET
Returns, for each related entity id given, how many emails the history holds for it, the status of the most recent one and when it was sent. Lets you show the state of an entity's email without loading its full history. - **`last_status`:** carries whatever the latest attempt ended in, `REJECTED` and `QUEUED` included, so a `count` above zero does not mean an email reached anyone. - **Ids with no associated emails:** omitted from the response rather than returned with `count` 0. - **Deprecated:** use `GET /v1/accounts/{account_id}/email-indicators`, which behaves identically. The successor is a sibling of the email collection, not `…/emails/indicators`: `indicators` used to sit where an email id goes. **Retires on 9 December 2026.** See the [migration guide](https://docs.beel.es/changelog/resources-under-the-nif) for what moved where and what changes when you switch.
All error codes
Every error code returned by the BeeL. API in one flat table — useful as a cheat sheet or to import as constants in your codebase.