Errors

Errors return JSON with an explanatory error string. Format

{ "error": "<message>" }

Structured errors To enable machine-readable handling, responses also include structured fields:

{ "code": "<error_code>", "message": "<message>", "error": "<message>", "details": {} }

Common codes

Code	Meaning
invalid_key	Missing or invalid API key
missing_scope	Key lacks required scope
validation_error	Invalid or missing fields
rate_limited	Per-minute cap exceeded
tenant_paused	Organization tenant is paused
not_found	Resource not found
internal_error	Provider/internal error

Statuses

Status	Meaning	Typical cause
400	Invalid or missing fields	Request body/params validation failed
401	Missing or invalid API key	Omitted/incorrect key or signature
403	Forbidden (missing scope/tenant restriction)	Scope not granted, tenant paused
404	Not found	Resource doesn’t exist
429	Rate limit exceeded	Per‑minute key limit exceeded (see Retry-After)
500	Provider/internal error	Transient or internal failure

Examples

{ "error": "Missing required fields" }
{ "error": "Invalid API key" }
{ "error": "Forbidden: missing scope send_email" }
{ "error": "Tenant paused for this organization" }

Request ID

All responses include X-Request-Id to help correlate logs and support requests.

Email support@fluxomail.com with your sendId and timestamp.

Planned improvements

See the API Roadmap for structured error fields (code/message/details) and migration guidance.

API documentation

Endpoints