Skip to main content

​
Errors

We expose API errors in two ways: standard HTTP response code and a more detailed JSON format. For example, the following code snippet shows an HTTP 404 error in the response headers: 
HTTP/2 404
date: Sat, 11 Aug 2018 18:08:08 GMT
content-type: application/json; charset=utf-8
content-length: 61
access-control-allow-origin: *
access-control-allow-methods: GET,HEAD,PUT,PATCH,POST,DELETE
access-control-allow-headers: Origin,Content-Type,Accept,Authorization,total-count,page-count
etag: W/"3d-qtDvRirKA9JoksEsKn0JpUa7cpg"
And this snippet shows the error as JSON object: 
{
  "error": {
    "code": "NOT FOUND",
    "message": "Customer not found"
  }
}
For HTTP response code, 4xx code suggest bad request. If you received a 4xx response, we recommend reviewing the api-reference for more context to help you troubleshoot. 5xx errors suggest a problem on Dintero’s end. You’re welcome to contact our support team on any 5xx errors. If you contact support we recommend including the complete request you’re trying to make and the error code and response you’re receiving so they can help as quickly as possible.

​
Downtime & Status page

Dintero API has a 99.99% uptime. We’re rarely offline for planned maintenance, for example as part of major releases. We have a status page for our services. You can subscribe to incidents through the Status Page.

​
Support

To start, we recommend reviewing the errors section in this guide, and method-specific errors for the endpoint you’re trying to access. If you’re seeing a 5xx error, that likely means there’s an error on Dintero side and you can contact our support team.
Last modified on May 11, 2026