HTTP Status Codes

The following are the HTTP status codes that may be encountered when using the Actionstep API.

Code	Status Text	Description
200	OK	Standard success response. GET responses will return the resource being requested. POST responses will return the resource that has been acted upon.
201	Created	A new resource has successfully being created. The response will contain the newly created resource as though it had been requested using the GET method.
204	No Content	Successfully processed request but not information is being returned. Often used when resources are being deleted. May occur if there are no records matching the requested filters.
400	Bad Request	Badly structured request that cannot be fulfilled.
401	Unauthorized	Similar to 403, but specific to the authorization that has either failed, or has not yet been provided.
403	Forbidden	Vaild request, but the server is refusing to respond to it.
404	Not Found	The requested resource could not be found but may be available again in the future. Subsequent requests to this resource are permissible.
405	Method Not Allowed	A request was made to a resource that doesn't support the request method used.
406	Not Acceptable	Unable to generate content according to the requested Accept headers.
415	Unsupported Media Type	Unsupported media type by the resource or server.
500	Internal Server Error	General error message given when an unexpected condition is encountered.
503	Service Unavailable	The server is currently unavailable. This is a temporary state.

Actionstep Error Codes

Actionstep specific error codes are group into the following general categories and may be returned with one of the above HTTP status codes, most commonly 500 Internal Server Error.

Code Group	Description
1100	Errors to do with routing the Request.
1200	Errors to do with building the Response.
1300	Errors to do with handling the Request.
1400	Undefined.
1500	Errors to do with the requested Resources.

Browser not supported