HTTP response codes
Following your webservice request, you will obtain a HTTP code in order to inform you of the status of the request. If the request failed, it will be an error code which will help you determine what to do in order to rectify this error.
For each operation, the status code typically expected will be indicated at the bottom of the interface. This is however not a comprehensive list. Codes that might be encountered are explained in the following practical guide:
Response codes
200 OK
This is the general success code. This is the most common code, which indicates that the request was processed successfully.
201 CREATED
This code signals that the creation happened successfully (through a POST or PUT method). The 'Location header' field will contain a link towards the newly created resource. According to the case, there might be content in the 'Response body' field.
204 NO CONTENT
This code signals that the request was processed successfully but that there is no content in the "Response body" field. This is typically the case with the DELETE and PUT methods.
400 BAD REQUEST
This the general code to signal that the request leads to an invalid result. This might be because of validation domain errors, missing data,...
Repeating the request without modifying its syntax is useless, as it would result in the same error code.
401 UNAUTHORIZED
This code signals that the authentication parameters required for using the API are missing or invalid.
This is also the response when an access token has expired after 15 minutes.
403 FORBIDDEN
This code is used when the user is not authorized to carry out the operation.
404 NOT FOUND
This code is used when the requested resource could not be found.
It may also act as a general error code, for instance if the service does not want to display a 401 or 403 code for security reasons.
405 METHOD NOT ALLOWED
This code signals that the request URL exists, but that the HTTP method of your call cannot be applied. For instance, a 405 code will be obtained if one tries to use a POST method when the API does not accept this kind of method.
409 CONFLICT
This code signals that complying to this request will create a conflict when it comes to the resource. This might for example involve duplicates, such as trying to create two profiles with the same information through a PUT method, or when one tries to delete a root object when cascade deletion is not supported.
The source of the conflict will be indicated in the response to the request.
429 TOO MANY REQUESTS
This code signals that you submitted too many requests concurrently or within a too short time span. Actito allows a maximum of 5 requests concurrently. If you encounter this error, we advise you to buffer your calls, to only launch a 6th request after one of the 5 first calls has received a response. A 429 error can also be encountered if you've reached the bulk imports limit.
500 INTERNAL SERVER ERROR
This is the general error message when the server encounters an unexpected condition that prevent it from complying with the request. This code is never displayed intentionally, but only for errors that you cannot influence on your side.
All 4XX errors suggests that something is wrong with your call and that it can be solved by investigating it.
A persisting error 500 will however probably require you to contact our support.