The Fuse API adheres to standard HTTP response codes to indicate the outcome of a request. In the event of a failure, additional error messaging will be provided within the response body to assist in troubleshooting. The error will be in the following format:
"title": "Aggregator Error",
"details": "An error occurred while communicating with an aggregator, see data for details",
"title": "MX Error",
"details": "Couldn't find User record(s) with the information provided.",
|Title of the error
|Details of the error
|Error code, see below for possible error codes and how to handle them.
|Possible values are
SERVER_ERROR. These error types provide a high-level categorization of the errors that can occur while interacting with the Fuse API.
AUTH_ERROR indicates an authentication-related issue, such as missing or invalid credentials.
NOT_FOUND means the requested resource could not be found.
BAD_REQUEST signifies that the client's request was malformed or contained invalid data.
SERVER_ERROR represents a general server-side error that occurred while processing the client's request.
|Possible values are
aggregator. Indicates the source of the error.
internal means the error is from Fuse internal server,
aggregator means the error is from an external financial connection aggregator like plaid, mx, teller etc.
array of FuseError objects
|An array of errors from an aggregator.
|200 - OK
|Everything worked as expected with content returned.
|400 - Bad Request
|The request was unacceptable, often due to missing a required parameter.
|401 - Unauthorized
|No valid API key provided.
|402 - Request Failed
|The parameters were valid but the request failed.
|403 - Forbidden
|The API key doesn't have permissions to perform the request.
|404 - Not Found
|The requested resource doesn't exist.
|429 - Too Many Requests
|Too many requests hit the API too quickly. We recommend an exponential backoff of your requests.
|500 - Server Errors
|Something went wrong with Fuse or upstream aggregator servers
Below outlines the different error codes that can be returned by the Fuse API. These error codes help clients understand the nature of the issues that might arise while using the API.
|The request headers provided by the client are invalid
|Request body is required but missing.
|The request is missing the access token.
|The request body is missing from the client's request.
|Invalid Content-Type header. Must be
|Request body is not a valid JSON format.
|A generic server-side error that occurred while processing the request.
|The Plaid client ID header is missing from the request.
|The Plaid secret header is missing from the request.
|The Plaid verification header is missing from the request.
|The MX client ID header is missing from the request.
|The MX API key header is missing from the request.
|The Teller private key header is missing from the request.
|The Teller certificate header is missing from the request.
|The Teller application ID header is missing from the request.
|The Teller signing secret header is missing from the request.
|The Teller signature header is missing from the request.
|The Fuse verification header is missing from the request.
|A generic aggregator error occurred. This error type will contain embedded error codes from the specific aggregator (such as Plaid, Teller, or MX) if they are unable to perform an action like retrieving balances. In such cases, the client should handle it or display a generic error message to the user.
Plaid has well documented errors on this.
|The aggregator has been disconnected from the account and the bank account needs to be reconnected.
|Access to the financial institution has been revoked and cannot be reestablished automatically. In the event that the user returns to your application, a new financial connection must be initiated and established for the user to regain access to their financial data.
|An error occurred while processing a webhook event.
Clients should handle these error codes and display appropriate error messages to their users. If clients encounter any aggregator errors that they find interesting or believe Fuse can resolve, they should report the issues to Fuse.
Fuse tracks these errors internally to determine the most reliable aggregator for each bank connection. This information is used to update the decision engine, which selects the best aggregator for each customer's user based on their bank connection.