Support Center

API Error Codes

Last Updated: Jan 08, 2016 03:21PM EST
NOTE: Redirecting to updated article at

What are API Error Codes and what do they mean?
As a web service, the Semantria API follows common HTTP principles and will respond with appropriate status codes with each request. The front-end application API only overrides 10 HTTP statuses with custom logic and messages, while the rest remain default. The custom statuses are as followed:

200 Server request correct and accepted. The server responds with data according to the document sent and the configuration of the auto response feature.
202 Server request correct and accepted. Server doesn’t respond with any data and just serves the request.
400 Wrong request format. Server responds with details.
401 Authentication failed.
402 Request is unauthorized. The number of calls limit has been reached or the license is expired.
403 Performed request is forbidden. Server responds with details.
404 No documents or collections with the provided unique configuration ID were found on the server.
406 Batch, collection or other configuration limits reached. Server responds with details.
413 Character limit for single document exceeded.
500 Server side issue. Server may respond with the details in response body.
HTTP statuses 400 and 500 are the only statuses that can have a differing description from that above. A 400 HTTP status signifies that here is a client-side issue and will include the details of the error. A 500 HTTP status signifies a server-side issue. Semantria may or may not respond with further details regarding the server-side issue, depending on the nature of the problem.
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
Invalid characters found