Skip to main content

HTTP Error Codes

This reference guide describes the HTTP error status codes returned by the Digital.ai Agility API and their common causes.

400 Bad Request​

A 400 status code is the most common error, resulting from a request that could not be processed by the API. The Error Message will identify the specific problem, and there may be Exception elements that give very detailed information. The usual causes of this error are:

  • An invalid parameter on the query string.
  • An invalid payload on a POST request.

401 Unauthorized​

A 401 status code indicates that the request could not be authenticated. This may be caused by any one of these conditions:

  • No credentials supplied to Basic Authentication, and no Authorization Ticket cookie sent with the request.
  • An invalid username or password was supplied to Basic Authentication.
  • An expired or invalid Authorization Ticket cookie sent with the request.

The typical course of action would be to include Basic Authorization credentials and resend the request.

404 Not Found​

A 404 status code indicates that there is no resource to retrieve at the requested URL. This could be due to:

  • An invalid URL path requested.
  • A request for a single asset which does not exist, or is deleted, or is secured from the user's view.

405 Method Not Allowed​

A 405 status code indicates that the HTTP method used for the request is not valid at the requested URL. This will be returned for any method other than GET and POST, or if POST was sent to a URL that does not support updating.

500 Internal Server Error​

A 500 status code indicates that an unexpected error occurred during the processing of the request. The response payload will contain Exception elements with specific information that will help technical diagnose the cause of the error. This could be due to:

  • An environmental problem (e.g., the database is unavailable).
  • An unhandled exception within the Digital.ai Agility software.