Troubleshooting

How To Troubleshoot API Errors

This sections covers the different error statuses you can get while using FusionFabric.cloud APIs. These API error message allow you to quickly find out why you’ve received a failed call.

The 4xx Response Codes

These response codes are client errors. These errors indicate that FusionFabric.cloud servers found an issue on your request.

401

The default message for this error is: {"statusCode": 401, "message": "Access token is missing or invalid."}. This response code is generated if a token is either missing or is invalid. To fix this, you must verify if your token information is correct.

403

This response code is generated in four different cases:

  1. The IP mentioned in the IP whitelist token claim does not match the client’s IP. The content of this claim is derived from the app definition. To fix this you must verify your whitelisted IP.
  2. The API is missing from the application. To fix this, you must add the API in the application.
  3. The scope claimed does not contain all the scopes mentioned at operations level, so the scope of the API is not authorized.
  4. The audience field is not set. To check if the audience field is not set, convert your token and check the aud parameter, which corresponds to your audience. This field could be blank if you’ve added the incorrect access token URL. If that is the case, you must check the URL in the API’s documentation.
404

The default message for this error is: {"statusCode": 404, "message": "Resource not found"}. This response code is generated only if a resourced is not found.

429

This response code occurs when an application makes a lot of calls in a couple of seconds.

The 5xx Response Codes

These response codes describe issues on the server’s side. You must check your response header to have more input about the 5xx response codes. With these header you could create, if necessary, a detailed ticket to our support team so we can detect it and solve it quickly.

502

This response code occurs in one of the following cases:

  • Tenant route alternate providers are not found, so no alternative provider is defined for the API.

  • The alternative providers for tenant routing are not found. This means that the provider indicated in the X-Finastra-provider header does not exist.

  • Tenant route not found. No backend is defined for the selected APIs or tenants.

503

This response code occurs in one of the following cases:

  • The token for tenant routing is unavailable. This means you cannot request a token to then receive the routing table.

  • Routing API is unavailable. The token is retrieved for the routing table, but cannot receive routing data.

  • Tenant routes are unavailable. This means no routes are defined for the selected tenant.

  • Security context is unavailable. This means that you cannot swap a token, the service is not up to security standards.

  • Security context contains an invalid token. This means that you cannot swap a token.