Here are the details of HTTP Failure Response within Fonoa API. Request errors are returned with HTTP status codes starting with 4xx and servers are starting with 5xx. Below is a partial list of responses.
| HTTP Result | Result | Description |
|---|---|---|
400 - Bad Request | Failure | The request was invalid due to invalid model validation. Developers are advised to check the response body message field for validation error messages. |
401 - Unauthorized | Denied | The request was not processed because the authorization credentials were not valid or acceptable for this resource. |
402 | Failure | Payment details must be set before this action can be taken. |
403 | Denied | The request was not processed because the authorization credentials do not allow access to the requested resource. |
404 - Not Found | Not Found | The resource you attempted to access is invalid. |
405 | Disabled | The request method is known by the server but has been disabled and cannot be used. |
406 | Not Acceptable | The input is not acceptable for this resource or for the field it was supplied with. |
408 | Timeout | The request timed out internally. Re-attempt the request. |
409 | Conflict | The request was rejected because of conflicting data or because it exceeded an internal limit. |
414 | Invalid | The request URI or headers exceeded the maximum length supported by the server. |
420 / 429 | Denied | The request may be valid but too many requests are being made. Slow down. |
423 | Temporarily Denied | The requested resource is locked temporarily. You should check the status of pending jobs. |
500 - Internal Server Error | Error | The request has failed internally and may be partially completed. These should be generated very infrequently. |
500 / 502 / 503 / 504 | Error | There is an internal outage in our stack. |