This document provides an overview of the type of error responses returned by our APIs.
The type of error responses you receive will vary by the endpoint you're using (or the type of request you’re making in the case of authentication and authorization). Rather than returning generic responses that offer little insight into the root cause of the problem, we provide tailored error responses per API. We also have a separate set of error responses for the authentication/authorization process.
Handling 500-level errors
We recommend implementing three (3) retries to help your app deal with short-lived, transient failures. The waiting time between retries should increase exponentially with each retry attempt.
Error responses returned deal with the following error states:
redirect_uriparameter is missing, or is unregisteredproviderIdis missing or incorrectclient_idis missing or incorrect- Server/subsystem errors
codeparameter (obtained during the authentication process) is incorrect or missingredirect_uriis missing or unregisteredgrant_typeis incorrect or missingclient_idand/orclient_secretis incorrect or missingrefresh_token,client_id, and/orclient_secretare missing, invalid, or claimed by another clienttoken_type_hintis not set torefresh_token
- Invalid input
- Invalid start or end date
- Invalid date range
- Customer not authorized
providerIdis incorrect, or your app does not have a subscription to that provider- Customer not found
- Account not found
- Account type not supported
- Server/subsystem errors
Please review the pages in this section for more details:
Need help?
Check out our Developer Community, or visit the Support Center in the Data Recipient Hub.
Looking for provider nuance documentation?
All provider nuance documentation is available in the Data providers section in the Data Recipient Hub.
Still stuck?
For all production issues, submit a support ticket through the Data Recipient Hub. Our support team is standing by 24/7. Questions and non-production issues will be answered during business hours.