Toda a documentação
DOCS api / error responses

Error Responses

HTTP errors and domain-specific error patterns.

Error Responses

The API uses standard HTTP status codes plus domain-specific error payloads.

Standard status codes

  • 200 OK: Request successful
  • 201 Created: Resource created
  • 204 No Content: Successful delete/revoke
  • 400 Bad Request: Validation or semantic request error
  • 401 Unauthorized: Missing or invalid auth
  • 403 Forbidden: Account access not allowed
  • 404 Not Found: Resource not found
  • 429 Too Many Requests: Rate limit or API key cap reached
  • 500 Internal Server Error: Server-side failure

Common error payload examples

{ "error": "Validation error", "details": { "...": "..." } }
{ "error": "monthly_limit_reached", "message": "Monthly post limit of 10 reached. Upgrade your plan to publish more posts." }
{ "error": "Unauthorized", "message": "Provide an Authorization: Bearer <token> header or X-API-Key header" }
{ "error": "Forbidden", "message": "Not a member of this account" }