Errors

The Addigence API uses conventional HTTP status codes and structured JSON error responses. This page documents the error formats and codes you may encounter.

Status codes

  • Name
    200 OK
    Description

    The request succeeded. The response body contains the requested data.

  • Name
    202 Accepted
    Description

    The request was accepted for processing (used when executing strategy versions). The response includes a Location header pointing to the created resource.

  • Name
    204 No Content
    Description

    The request succeeded with no response body (used for deletions).

  • Name
    400 Bad Request
    Description

    The request was malformed or contained invalid parameters (e.g., invalid scope).

  • Name
    401 Unauthorized
    Description

    Authentication failed — missing, invalid, or expired credentials or token.

  • Name
    403 Forbidden
    Description

    The token is valid but lacks the required scope for this action.

  • Name
    404 Not Found
    Description

    The requested resource does not exist, or belongs to a different organization.

  • Name
    422 Unprocessable Entity
    Description

    The request was well-formed but contained validation errors or could not be processed (e.g., unknown symbols, version already executed).

  • Name
    429 Too Many Requests
    Description

    Rate limit exceeded on the token endpoint. Wait before retrying.

  • Name
    500 Internal Server Error
    Description

    An unexpected server error occurred. Contact support if this persists.

Error formats

The API uses two distinct error response formats depending on the type of error.

Authentication and authorization errors

Token exchange errors, invalid/expired tokens, and scope errors return an OAuth2-style error object at the top level:

  • Name
    error
    Type
    string
    Description

    A machine-readable error code. See the table below.

  • Name
    error_description
    Type
    string
    Description

    A human-readable explanation of what went wrong.

Error codes

  • Name
    invalid_client
    Description

    The client_id or client_secret is incorrect, the client does not exist, or the client has been revoked.

  • Name
    invalid_scope
    Description

    The requested scopes are not a valid subset of the client's allowed scopes.

  • Name
    invalid_token
    Description

    The bearer token is missing, malformed, expired, or belongs to a revoked client.

  • Name
    insufficient_scope
    Description

    The token does not have the required scope for this action.

  • Name
    rate_limited
    Description

    Too many token requests from this IP address. Wait 5 minutes before retrying.

Examples

{
  "error": "invalid_client",
  "error_description": "Invalid client credentials"
}

Validation errors

Resource endpoints return validation errors in an errors object, where keys are field names and values are arrays of error messages:

  • Name
    errors
    Type
    object
    Description

    An object mapping field names to arrays of error message strings. For non-field-specific errors, the key is "detail".

Examples

{
  "errors": {
    "positions": ["can't be blank"]
  }
}