HTTP status codes | API

As a general rule HTTP status codes can be interpreted as follows:

1xx informational response – the request was received, continuing process

2xx successful – the request was successfully received, understood, and accepted

3xx redirection – further action needs to be taken in order to complete the request

4xx client error – the request contains bad syntax or cannot be fulfilled

5xx server error – the server failed to fulfil an apparently valid request

Common Credas response codes

400

Bad request, indicates missing mandatory request fields or malformed request syntax. 

401

Unauthorized, confirm the API key you are using is valid and directed at the correct base URL. 

403

Forbidden, confirm you have the correct permissions assigned to your client or client user account for the endpoint you are using. 

404

Requested file/page not found by server, indicated an incorrect base URL or endpoint is being used. 

405

Method not allowed, indicates an incorrect request method is being used (e.g. POST not PUT).

500

This is a generic internal server error, if the issue persists please contact Credas. 

503

This is generic server unavailable, if the issue persists please contact Credas.