The table below restores the general status reference from the original documentation. Each endpoint lists its documented responses.
Allowed request types
-
POST - Creates or updates a resource
-
PUT - Updates a resource
-
GET - Retrieves a resource or list of resources
-
DELETE - Delete a resource
Response status codes
| Status | Meaning | What to check |
|---|---|---|
200 |
OK | Check response body for errors |
201 |
Created | Check response body for errors |
204 |
No Content | Response for delete request |
400 |
Bad Request | The request could not be processed because it contains missing or invalid information (such as validation error on an filter field, a missing required value) |
401 |
Unauthorized | Disabled API feature or invalid connection credentials. |
402 |
Payment Required | Check web interface for billing info, billing action may be required |
403 |
Forbidden | You have no access to resource |
404 |
Not Found | Check request URL and HTTP method or agenda/document is not available, check response body for errors |
406 |
Not Acceptable | Most probably malformed content type header or json body |
422 |
Unprocessable Entity | The request was well-formed but was unable to be followed due to semantic or validation errors. |
429 |
Too Many Requests | The request rate exceeded the applicable limit. Slow down and retry with backoff. Confirm your integration’s limit with Datamolino before sizing a bulk import. |
500 |
Internal Server Error | The server encountered an unexpected condition which prevented it from fulfilling the request |
501 |
Not Implemented | The server does not (currently) support the functionality required to fulfill the request |
502 |
Bad Gateway | The server was acting as a gateway or proxy and received an invalid response from the upstream server. Check request parameters. |
503 |
Service Unavailable | Overloaded API or scheduled maintenance in progress. Try again later. |
504 |
Gateway Timeout | API request timeout |
Handling errors
Inspect the response body as well as the HTTP status. A 204 No Content response has no body. Use the endpoint’s request and response examples alongside this general reference.