Error Codes

The Daxium-Air API uses standardized error codes prefixed with DAERR- to identify specific errors. Each returned error includes an appropriate HTTP code, a descriptive message, and contextual information.

Error Response Format

All errors follow a standardized JSON structure:

{
  "code": "DAERR-API1000",
  "message": "Invalid payload format",
  "url": "https://doc-dev.daxium-air.com/errors.en.html#DAERR-API1000",
  "api_version": "v1.3",
  "infos": [],
  "server_time": "1760616000"
}

Response Structure

API Error Codes

DAERR-API1000

HTTP 400 Bad Request

Message: Invalid payload format

Cause: The request contains a malformed payload or its structure does not match the expected format.

Solution: Verify that your JSON payload is valid and matches the structure expected by the endpoint.

DAERR-API1001

HTTP 404 Not Found

Message: User not found

Cause: The provided email address does not match any user in the system.

Solution: Check the email address and ensure it corresponds to an existing user.

DAERR-API1002

HTTP 404 Not Found

Message: Route not found

Cause: The requested endpoint does not exist in the API.

Solution: Check your request URL and consult the documentation to use the correct endpoint.

DAERR-API1003

HTTP 404 Not Found

Message: Structure not found

Cause: The requested structure does not exist or is not accessible with your permissions.

Solution: Verify the structure ID and ensure you have the necessary permissions.

Authentication Error Codes

DAERR-LOG013

HTTP 429 Too Many Requests

Message: Too many login attempts

Cause: The account has been temporarily locked due to excessive failed login attempts.

Solution: Wait a few minutes before trying again. If the problem persists, use the password reset feature.

DAERR-LOG014

HTTP 429 Too Many Requests

Message: Too many password reset requests

Cause: An excessive number of password reset requests has been detected for this account.

Solution: Wait a few minutes before submitting a new request.

SSO SAML Error Codes

DAERR-SSO1000

HTTP 400 Bad Request

Message: Missing parameter

Cause: One or more required parameters are missing from the SSO request.

Solution: Check the SSO documentation and ensure all required parameters are included.

DAERR-SSO1001

HTTP 400 Bad Request

Message: Invalid client ID

Cause: The provided client ID is invalid or does not exist.

Solution: Verify your SSO configuration and the provided client ID.

DAERR-SSO1002

HTTP 403 Forbidden

Message: Empty username

Cause: The username was not provided or is empty.

Solution: Ensure the username is correctly transmitted via the SSO flow.

DAERR-SSO1003

HTTP 403 Forbidden

Message: User not found

Cause: The user does not exist in the system.

Solution: Verify that the user exists and is correctly configured for SSO authentication.

DAERR-SSO1004

HTTP 403 Forbidden

Message: User not allowed

Cause: The user exists but does not have the necessary permissions to access via SSO.

Solution: Contact the administrator to verify the user's permissions.

DAERR-SSO1005

HTTP 403 Forbidden

Message: Invalid redirect URI

Cause: The provided redirect URI is not authorized for this application.

Solution: Verify that the redirect URI is configured in the application's SSO settings.

DAERR-SSO1007

HTTP 400 Bad Request

Message: Invalid logout request

Cause: The SAML logout request is not valid.

Solution: Check the format of the SAML logout request.

DAERR-SSO1008

HTTP 400 Bad Request

Message: Invalid logout XML

Cause: The XML of the SAML logout request is malformed.

Solution: Ensure the logout request XML conforms to the SAML standard.

DAERR-SSO1009

HTTP 400 Bad Request

Message: Invalid SSO provider ID

Cause: The SSO provider ID is not valid.

Solution: Verify the SSO provider ID in your configuration.

DAERR-SSO1010

HTTP 400 Bad Request

Message: Invalid SAML configuration

Cause: The SAML configuration parameters are incorrect or incomplete.

Solution: Review the SAML configuration and ensure all required parameters are properly defined.

DAERR-SSO1011

HTTP 404 Not Found

Message: Invalid provider

Cause: The specified SSO provider does not exist.

Solution: Verify that the SSO provider is correctly configured in the system.

DAERR-SSO1012

HTTP 404 Not Found

Message: User not found during logout

Cause: The user could not be identified during the logout attempt.

Solution: Verify that the user is logged in and session information is valid.

SSO OpenID Connect Error Codes

DAERR-SSO100

HTTP 400 Bad Request

Message: User not found (OpenID)

Cause: The OpenID Connect user was not found in the system.

Solution: Verify that the user exists and the OpenID mapping is correctly configured.

DAERR-SSO101

HTTP 403 Forbidden

Message: Access denied (OpenID)

Cause: Access via OpenID Connect was denied.

Solution: Check the user's permissions and OpenID Connect configuration.

DAERR-SSO102

HTTP 400 Bad Request

Message: Incorrect provider type

Cause: The provider is not of OpenID Connect type.

Solution: Use a valid OpenID Connect provider.

DAERR-SSO103

HTTP 400 Bad Request

Message: Missing IDP

Cause: The Identity Provider (IDP) is not configured.

Solution: Configure a valid OpenID Connect Identity Provider.

DAERR-SSO104

HTTP 400 Bad Request

Message: Missing Client ID

Cause: The OpenID Connect Client ID is not configured.

Solution: Add the Client ID in the OpenID Connect configuration.

DAERR-SSO105

HTTP 400 Bad Request

Message: Missing Client Secret

Cause: The OpenID Connect Client Secret is not configured.

Solution: Add the Client Secret in the OpenID Connect configuration.

DAERR-SSO106

HTTP 400 Bad Request

Message: Error from provider

Cause: The OpenID Connect provider returned an error.

Solution: Consult the OpenID Connect provider logs for more details about the error.

DAERR-SSO107

HTTP 404 Not Found

Message: Provider not found

Cause: The specified OpenID Connect provider does not exist.

Solution: Verify the provider identifier in your configuration.

DAERR-SSO108

HTTP 400 Bad Request

Message: Invalid username

Cause: The username received from the OpenID Connect provider is not valid.

Solution: Check the OpenID Connect attribute mapping and ensure the username claim is correctly configured.

Filter Error Codes

DAERR-FIL1000

HTTP 500 Internal Server Error

Message: Generic filter error

Cause: A generic error occurred while processing the filter.

Solution: Check your filter structure and contact support if the problem persists.

DAERR-FIL1001

HTTP 400 Bad Request

Message: Bad metadata combination

Cause: The filter metadata contains an invalid combination of parameters.

Solution: Review your metadata structure and ensure it follows the combination rules.

DAERR-FIL1002

HTTP 400 Bad Request

Message: Bad parameter combination

Cause: The filter parameters contain an invalid combination.

Solution: Verify that your parameters follow the allowed combinations.

DAERR-FIL1003

HTTP 400 Bad Request

Message: Null value and "equal to" not allowed

Cause: You cannot use the "equal to" operator with a null value.

Solution: Use the "is empty" operator to test for null values.

DAERR-FIL1004

HTTP 400 Bad Request

Message: Null value and "not equal to" not allowed

Cause: You cannot use the "not equal to" operator with a null value.

Solution: Use the "is not empty" operator to test for non-null values.

DAERR-FIL1005

HTTP 400 Bad Request

Message: Missing field in criterion

Cause: A filter criterion does not contain a field.

Solution: Add a valid field to each criterion in your filter.

DAERR-FIL1006

HTTP 400 Bad Request

Message: Missing field

Cause: The specified field is missing from the filter request.

Solution: Add the required field to your filter.

DAERR-FIL1007

HTTP 400 Bad Request

Message: Incorrect metadata type

Cause: The metadata type does not match the expected type.

Solution: Verify the metadata types in your filter.

DAERR-FIL1008

HTTP 400 Bad Request

Message: Incorrect parameter type

Cause: The parameter type does not match the expected type.

Solution: Correct the parameter type in your filter.

DAERR-FIL1009

HTTP 400 Bad Request

Message: Operator not allowed for metadata

Cause: The operator used is not compatible with this metadata type.

Solution: Consult the documentation for allowed operators for this metadata type.

DAERR-FIL1010

HTTP 400 Bad Request

Message: Operator not allowed for parameter

Cause: The operator used is not compatible with this parameter type.

Solution: Use an operator compatible with the parameter type.

DAERR-FIL1011

HTTP 400 Bad Request

Message: Missing structure

Cause: The filter requires a structure but none is specified.

Solution: Add a structure reference to your filter.

DAERR-FIL1012

HTTP 400 Bad Request

Message: Unsupported entity type

Cause: The specified entity type is not supported for filtering.

Solution: Use an entity type supported by the filtering system.

DAERR-FIL1013

HTTP 400 Bad Request

Message: Invalid JSON

Cause: The filter JSON is malformed.

Solution: Validate the JSON syntax of your filter.

DAERR-FIL1014

HTTP 400 Bad Request

Message: Incorrect field type

Cause: The field type does not match the expected type.

Solution: Check the field type in the structure and adapt your filter.

DAERR-FIL1015

HTTP 400 Bad Request

Message: Duplicate UUID

Cause: A UUID is used multiple times in the filter.

Solution: Ensure each UUID is unique in your filter.

DAERR-FIL1016

HTTP 400 Bad Request

Message: Referenced UUID does not exist

Cause: A UUID referenced in the filter does not exist.

Solution: Verify that all referenced UUIDs exist in your filter.

DAERR-FIL1017

HTTP 400 Bad Request

Message: Field does not exist

Cause: The specified field does not exist in the structure.

Solution: Use an existing field in the targeted structure.

DAERR-FIL1018

HTTP 400 Bad Request

Message: Missing composition

Cause: The filter composition is missing or incomplete.

Solution: Add a valid composition to your filter.

DAERR-FIL1019

HTTP 400 Bad Request

Message: Identifier does not exist

Cause: The specified identifier does not exist.

Solution: Use a valid and existing identifier.

DAERR-FIL1020

HTTP 400 Bad Request

Message: Composition operator does not exist

Cause: The composition operator (AND/OR) is not recognized.

Solution: Use only valid composition operators (AND, OR).

DAERR-FIL1021

HTTP 400 Bad Request

Message: Metadata name does not exist

Cause: The specified metadata name does not exist.

Solution: Use a valid metadata name.

DAERR-FIL1022

HTTP 400 Bad Request

Message: Bad exhaustive combination

Cause: The exhaustive filter parameters contain an invalid combination.

Solution: Review the exhaustive parameter configuration.

DAERR-FIL1023

HTTP 400 Bad Request

Message: Missing field in parameter order by

Cause: A field is missing in the ORDER BY clause on a parameter.

Solution: Add the required field to your sort clause.

DAERR-FIL1024

HTTP 400 Bad Request

Message: Missing field in metadata order by

Cause: A field is missing in the ORDER BY clause on metadata.

Solution: Add the required field to your sort clause.

DAERR-FIL1025

HTTP 400 Bad Request

Message: Sort order does not exist

Cause: The specified sort order is not valid.

Solution: Use "ASC" or "DESC" for the sort order.

DAERR-FIL1026

HTTP 400 Bad Request

Message: Missing field in sort

Cause: The sort field is missing from the ORDER BY clause.

Solution: Specify a field for sorting.