Coinbase Cloud API Errors

Coinbase Cloud APIs attempt to follow a standard convention for error handling and reporting. Server errors, and errors generated before the API service receives a request, are reported using standard HTTP Response Codes. Supplemental details may be included in the response Body. Errors returned by APIs usually map to the appropriate HTTP Response Codes, otherwise they are a generic 400. In addition to the response code, the response Body is a JSON object with supplemental details of the form: { ‘message’: ‘error message’ }. Error messages are intentionally sanitized to avoid revealing sensitive information or implementation details.

Standard Response codes:

200	OK	Everything is working
201	OK	New resource has been created
204	OK	The resource was successfully deleted
304	Not Modified	The client can use cached data
400	Bad Request	The request was invalid or cannot be served. The exact error should be explained in the error payload, e.g., "The JSON is not valid"
401	Unauthorized	The request requires a user authentication
403	Forbidden	The server understood the request but is refusing it or the access is not allowed.
404	Not found	There is no resource behind the URI.
422	Unprocessable Entity	Should be used if the server cannot process the entity, e.g., if an image cannot be formatted or mandatory fields are missing in the payload.
500	Internal Server Error	API developers should avoid this error. If an error occurs in the global catch blog, the stack trace should be logged and not returned as in the response.