Errors

Error responses follow a consistent structure so that you can implement reliable handling logic.

Standard error format

All API errors return a consistent JSON structure:

{
  "message": "Quota exceeded: maximum 20 API keys allowed per organization (currently: 20)",
  "statusCode": 403,
  "error": "Forbidden"
}

Domain-specific errors

Domain specific errors also include a machine readable code field to help you handle specific error conditions:

{
  "code": "INVALID_EXPIRATION",
  "message": "Expiration cannot be more than 86400 seconds from now"
}

Validation errors

Validation errors return an array of messages in the message field, allowing you to display multiple validation issues to your users:

{
  "message": [
    "name must be a string",
    "name should not be empty",
    "expiration must be a valid ISO 8601 date string"
  ],
  "error": "Bad Request",
  "statusCode": 400
}

OpenAPI schema

You can inspect the OpenAPI components named StandardErrorResponseDto to see the complete error schema definition at https://api.reeflow.com/openapi.