HTTP status codes

Owned by Jens De Pelsmaeker
Last updated: Oct 27, 2021
2 min read

We have a number of status codes in use in our product. Below is an overview of the common ones with some basic explanations for each. The response’s content-type we send is by default “application/json” (but may in exceptional cases depend on the requested content type by the sender).

200/201

Success: the operation succeeded as intended

400

The operation failed because of invalid user input. The error message explains how the used input was different from what was expected

401

Unauthorised: these credentials are invalid.

403

Insufficient permissions: this user does not have the required permissions to access this endpoint

404

Not Found: this resource cannot be found in our DB

405

Method Not Allowed: this operation is not allowed for this endpoint

409

Conflict: This request causes a conflict on our end

413

Payload too large: this file exceeds our page limit of 200 pages or size of 100 Mb

415

Unsupported Media Type: we do not support processing files of this file type

422

Unprocessable entity: the payload is corrupt or unreadable; we cannot understand this request and therefore are unable to process it

429

Too many request: we temporarily need to limit requests due to high load

500/501

Internal Server Error: this category contains various errors that might occur in the application on our end

502

Gateway timeout: this error will occur when the operation is taking longer than a fixed timeout threshold (default is 300 seconds)

 

 

Full list from API Reference (slate)

https://alfredo.contract-p.fit/slate/#errors