Fusable API Error Handling

Error Handling

Please refer to the section below to understand API error responses with possible reasons and resolution steps. If the problem persists, please don't hesitate to contact us for additional support. 

HTTP 400 : Bad request

Please refer to the API contract and make sure the request is valid. Refer to the resource operation summary in swagger or postman for an example request. Check the error message in the bad request response body for the actual error description.

Resolution:

• Make sure all the required input parameters are present in the API request.
• Make sure the values are the appropriate data type and format required.
• Make sure the request is in an appropriate JSON format.

HTTP 401 : Unauthorized

Error most likely due to an invalid access token or access token has expired. The token expires after 2 hours.

Resolution:

• Confirm the right client_id and client_secret are used to get a new access token
• Confirm access token is not expired ,missing or incorrect in the API request.

HTTP 403 : Forbidden / Missing license

The server has received and understood the request, but it is refusing to allow it. Error code message will return either “Forbidden” or “Missing license for endpoint.”

Resolution:

• For “Forbidden” message: typically occurs when a request has been blocked by the WAF. Check calls against rate limits.
• For “missing license” message:
  • Confirm request included only endpoints and data packages included in your license subscription
  • Contact Fusable support if you are expecting access to an endpoint or data package that is missing permissions.

HTTP 404 : Invalid Path

The URL path specified in the request is incorrect or does not map to any existing resource on the server.

Resolution: Check the resource operation summary and swagger for API request examples and to get the correct endpoint URL path

HTTP 429 : Too many requests

Indicates that too many requests have been sent in a given period and is being rate limited. The client side should Implement request throttling and have a retry logic to send the request after some time.

Resolution:

• Check the Rate Limits above to make sure not to exceed the throttling limits:
  • The Fusable API is rate limited at 4500 requests every 5 minutes, or 15 requests per second.
  • The Fusable API request processes will time out after 29 seconds. Note Bulk endpoints run asynchronously.
  • Bearer tokens are valid for 2 hours. It is recommended the token be cached in any integration to minimize the volume of authentication requests per client.
• Retry the request after some time has passed

• Authentication tokens are valid for 2 hours. Cache the token to minimize authentication calls

HTTP 500 : Internal Server Error

A 500 Internal Server Error is a generic server-side error indicating that the server encountered an unexpected condition that prevented it from fulfilling the request

Resolution: Please contact Fusable Support to report the issue if you see this response code.