HTTP Status Codes
HTTP status codes are used to indicate the status of a request.Success Response (200 - 299)
The following status codes indicate a successful response.| Response Status Code | Description |
|---|---|
| 200 OK | The synchronous task executed successfully and returned the result. |
| 201 Created | The task was created successfully and a new resource was created (e.g., a session). |
| 202 Accepted | The request has been accepted but not yet processed; it does not indicate the final outcome (e.g., creation of an asynchronous task). |
| 201 Created | The task was created successfully and a new resource was created (e.g., a session). |
| 202 Accepted | The request has been accepted but not yet processed; it does not indicate the final outcome (e.g., creation of an asynchronous task). |
Client Error Response (400 - 499)
The following status codes indicate a client error.| Response Status Code | Description |
|---|---|
| 400 Bad Request | Invalid request parameters (e.g., malformed body, incorrect fields). |
| 401 Unauthorized | Unauthorized (e.g., token expired or invalid). |
| 403 Forbidden | Forbidden (e.g., insufficient permissions to access the resource). |
| 404 Not Found | The requested resource was not found (e.g., incorrect path). |
| 405 Method Not Allowed | Method not allowed (e.g., attempting to create an async task via a synchronous endpoint). |
| 409 Conflict | Conflict (e.g., attempting to create an asynchronous task that already exists). |
| 423 Locked | The requested resource is locked (e.g., attempting to write to a resource that is currently being written). |
| 429 Too Many Requests | Too many requests (e.g., rate limit or quota exceeded). |
| 451 Unavailable For Legal Reasons | Unavailable for legal reasons. |
Server Error Response (500 - 599)
The following status codes indicate a server error. You can try again later. If error continues, please contact us for assistance.| Response Status Code | Description |
|---|---|
| 500 Internal Server Error | Server error (e.g., an unknown error occurred on the server). |
| 502 Bad Gateway | Bad gateway (e.g., an upstream service returned an error). |
| 503 Service Unavailable | Service unavailable (e.g., our service is experiencing an outage). |
MuleRouter Errors
When an asynchronous task request fails, MuleRouter will return an RFC 7807 formatted error body.HTTP Status Code. Refer to HTTP Status Codes for more details.
Short title of the error
MuleRouter Error Code. Refer to MuleRouter Error Codes for more details.
A URI reference that identifies the specific occurrence of the problem.
A URI reference that identifies the problem type.
Description of the error