All calls to the authentication service or to the other API entry points may return errors which need to be handled. Error coding adopts the standard HTTP error codes, messages and structure.

{
  "message": "Invalid token: access token is invalid",
  "code": 401,
  "name": "invalid_token"
}

When calling a service, you correctly passed a token header but the token it contains is invalid. Check your code to make sure that you are returning the token which was sent back by the authentication service.

{
  "message": "Unauthorized request: no authentication given",
  "code": 401,
  "name": "unauthorized_request"
}

When calling a service, you forgot to add a token header. Check your code to make sure that you are passing a token header when calling the service.

{
  "message": "Terms & Conditions have changed, please accept them to use this service",
  "code": 403,
  "name": "terms"
}

Terms and conditions of the TCD have not been accepted, or have changed and need to be accepted. Using the same <username> and <password> as those passed to the authentication service, log in manually into the TCD application (make sure you use the correct environment : sandbox or production) and accept the new terms and conditions.

{
  "body": "An alert or warning prevents you from querying this container",
  "code": 417,
  "name": "alert"
}

This container has been declared as sold or scrapped by his owner and should no longer be used for further operation.