Fusion APIs return standard error codes when an API operation fails to process a request payload. In such scenarios, error codes and their corresponding HTTP status codes help you troubleshoot the issue.
The sample error response below shows the HTTP response body structure that is returned in case of error:
HTTP Response Body: { "message": "Bad Request", "errorCode": "FU4000", "traceID": "ysiadfhi-fjksdabfkld-fahjksdlk", "additionalInfo": { "id": "should is missing", "email": "invalid email" } } HTTP Status Code: 400 |
traceId is a unique identity for any error that is generated. The same traceId gets logged and helps in faster debugging when you report an error. |
The following table lists the possible error codes returned on Fusion platform:
Error Code | HTTP Status Code | Error Code Description |
FU4000 | 400 | Bad Request |
FU4001 | 401 | Unauthorised |
FU4003 | 403 | Forbidden |
FU4004 | 404 | Not Found Page you are trying to access could not be found on the server as it might have been deleted or moved to a different location. |
FU4005 | 405 | Method Not Allowed |
FU4008 | 408 | Request Timeout Due to incorrect URI specified in the request, the page takes longer time to load. |
FU4009 | 409 | Conflict When the client is trying to upload the same file as in the server, then this results in version control conflict. |
FU4010 | 410 | Gone |
FU4012 | 412 | Precondition Failed |
FU4013 | 413 | Payload Too Large Request payload is too large for the server to accept and process it. |
FU4014 | 414 | URI Too Long |
FU4015 | 415 | Unsupported Media Type Format of the requested resource is not supported by the server. |
FU4017 | 417 | Expectation Failed |
FU4029 | 429 | Too Many Requests Client has sent too many API requests to the server. |
FU4051 | 451 | Unavailable For Legal Reasons |
FU5000 | 500 | Internal Server Error |
FU5001 | 501 | Not Implemented |
FU5002 | 502 | Bad Gateway |
FU5003 | 503 | Service Unavailable |
FU5004 | 504 | Gateway Timeout |
|