Skip to content

Error Codes

All errors return a JSON body with a detail field explaining what went wrong.

{
"detail": "Human-readable error message"
}
CodeMeaningWhen
200OKSuccessful read or update
201CreatedResource created successfully
204No ContentResource deleted successfully
400Bad RequestInvalid input or duplicate resource
403ForbiddenAuth failure or quota exceeded
404Not FoundResource doesn’t exist or not owned by you
422Unprocessable EntityValidation error, such as an invalid field value (for example an unknown warmup_profile)
500Internal Server ErrorUnexpected server-side error
DetailCauseFix
Invalid authorization header formatMissing Bearer prefixUse Authorization: Bearer YOUR_KEY
Invalid API keyToken not found in databaseCheck your API key
API key is deactivatedToken was revokedGenerate a new key
API key has expiredToken past expiration dateCreate a new key or update expiration
DetailCauseFix
Domain quota exceeded: 5/5All domain slots usedUpgrade plan or delete a domain
Mailbox quota exceeded for this domain: 3/3Domain mailbox limit reachedUpgrade plan or delete a mailbox
DetailCauseFix
El dominio ya existe en el servidor SaaSDomain name takenChoose a different domain
Este email (buzón) ya existe en el servidor SaaSEmail address takenChoose a different email
El dominio asociado no existeDomain not found for mailbox creationCreate the domain first
Dominio no encontradoDomain doesn’t exist or not yoursCheck the domain name
Usuario (buzón) no encontradoMailbox doesn’t exist or not yoursCheck the email address

These errors are returned by mx1.emboux.com while your application submits an email. Odoo shows them on the email.

ErrorCauseFix
553 5.7.1 Sender domain is not enabled to send through EmBoux: use an address of your EmBoux domain as envelope sender (Return-Path)The technical sender (Return-Path) belongs to a domain that is not enabled in EmBoux. In Odoo it is bounce@<mail.catchall.domain>.Set mail.catchall.domain to an enabled domain, then retry. Emails queued earlier keep the old sender and must be regenerated. See Align mail.catchall.domain.
550 5.7.1 Domain not verified. Configure DNS records first.The root domain is not verified and has no verified parent. Applies in any enforcement mode.Verify the domain and publish its DNS records. See Send as your own domain.
550 5.1.1The recipient is on the global suppression list (previous bounce or complaint). Only hard domains reject.Do not retry that address. Remove it from your list. See Suppression List.
452 4.2.2 Warm-up limit reached (<N>/day, profile=<profile>). Domain active for <D> days.The domain reached its daily warm-up cap.Retry later (the cap grows daily), spread your sends, or ask for a different warm-up category such as established if you have a sending history. See Warm-up Profiles.
452 4.2.2 (hourly, daily or monthly limit, unusual volume spike, or suspended domain)The domain exceeded a limit, sent an unusual spike of volume, or is suspended. Only hard domains reject.Retry later, spread your sends, or review your limits and outbound status. See Anti-Spam Protections.

A 452 is temporary: your server should retry it later. The 5xx errors are permanent and will not succeed on retry until the cause is fixed.

  1. Always check the status code before parsing the response body
  2. Retry on 500 errors with exponential backoff (max 3 retries)
  3. Don’t retry 400/403/404 — these are client errors that won’t resolve on retry
  4. Log the detail field for debugging — it contains specific information about what went wrong