DB Status Codes

Use status codes to verify standard behavior and to diagnose and remedy exceptions

Data Bridge indicates the success or failure of an API request with a status code. These status codes are displayed in the message body of the HTTP response.

HTTP response status codes enable you to verify normal behavior and provide context for understanding exceptions.

Data Bridge uses standard HTTP response codes to indicate the success or failure of an API request.

200 OK
An OK status indicates that the request was successful. A valid response has been returned.
201 Created
A Created status indicates that the entity requested has been created successfully.
202 Accepted
An Accepted status indicates that the request was accepted and queued but not executed.
204 No Content
A No Content status indicates that the request had No body content. Used for response to DELETE request.
304 Not Modified
The Not Modified status is used in combination with caching.
400 Bad Request
The Bad Request status indicates that there is a validation error or wrong parameters.
401 Unauthorized
The Unauthorized status indicates that the credentials are missing or invalid.
403 Forbidden
The Forbidden status indicates that Cannot access: Access Control, Licensing or Rate Limiting.
404 Not Found
The Not Found status indicates that the resource referenced does not exist.
405 Method Not Allowed
The Method Not Allowed status indicates that the resource/method combination is invalid.
409 Conflict
The Conflict status indicates that the representation conflicts with target resource state.
410 Gone
The Gone status indicates that the requested resource is no longer available at the server and no forwarding address is known.
415 Unsupported Media Type
The Unsupported Media Type error response indicates that the media format of the requested data is not supported by the server.
422 Unprocessable Entity (WebDav)
The Unprocessable Entity error response indicates that the request could not be processed to semantic errors.
429 Too Many Requests
The Too many requests status is used for rate limiting.
500 Internal Server Error
The Internal Server Error status identifies an unexpected condition has occurred.
501 Not Implemented
The server does not support the request method.
504 Gateway Timeout
The Gateway Timeout error response indicates that the server cannot get the response in time.