Response Codes

We use standard HTTP codes to denote a successful execution or error. For some errors, the response will include additional information about the error, including an application error code and a human readable error description.

Successful Execution

Operations that execute successfully will return a 200 code.

Operation Verb	HTTP Response Code	Response Body
POST	200	The corresponding JSON object

Error Handling - Error Codes

Operations that result in an error due to a problem on the client's part (e.g. invalid input) will produce standard 4xx codes.

The table below shows the HTTP response codes and entities used for some common error conditions:

Error Condition	HTTP Response Code	Response Body
The submitted data was invalid in some way	400	Failed to decode JSON object
The client API keys were not specified, or were not valid	Blank	Forbidden
Incorrect AWS Access Key	400	InvalidAccessKeyId
Incorrect AWS Secret Key	400	SignatureDoesNotMatchId
Incorrect S3 path	400	InvalidPathway