Standard HTTP Response Codes

Clarity NDC uses standard HTTP response codes to indicate the success or failure of API requests.

Code Reason Description
200 Success The request is successful.
400 Bad request The server was unable to process the request because of a missing or malformed parameter.
401 Invalid authentication The request requires user authentication. A valid authentication token was not provided with the request, so the API could not associate a user with the request. This could mean no token was provided, or the provided token was incorrect (or disabled).
404 Not found The server has found nothing matching the Request. Either the request method and path supplied do not specify a known action in the API, or the object specified by the request does not exist.
500 Internal error The server encountered an unexpected error, which prevented it from fulfilling the request.