Responses and Error Codes

The Erudus API supports GET, POST, PUT and DELETE HTTP methods for interacting with resources.

SSL

All endpoints require HTTPS.

JSON

The Erudus API supports JSON data format only. Most POST and PUT requests require a valid JSON object for the body. The responses generated by the API will also be in JSON format.

It is recommended to supply teh follwoing header when making API requests:

Accept    application/json

Status Codes

The Erudus API attempts to return appropriate HTTP status codes for every request.

200	OK	Success!
201	Created	The request has been fulfilled and resulted in a new resource being created.
204	No Content	The server successfully processed the request, but is not returning any content.
304	Not Modified	There was no new data to return.
400	Bad Request	The request was invalid or cannot be otherwise served.
401	Unauthorized	Authentication credentials were missing or incorrect.
403	Forbidden	The request is understood, but it has been refused or access is not allowed.
404	Not Found	The URI requested is invalid or the resource requested, does not exists.
406	Not Acceptable	Returned when an invalid format is specified in the request.
422	Unprocessable Entity	Returned when data validation fails.
429	Too Many Requests	Returned when rate limit is exhausted for the resource.
500	Internal Server Error	Something is broken. Please contact us and let us know.
502	Bad Gateway	Erudus is down or being upgraded.
503	Service Unavailable	Erudus may be up, but is overloaded with requests. Try again later.
504	Gateway timeout	Erudus is up, but the request couldn’t be serviced due to some failure within our stack. Try again later.