HTTP Status Code
This topic defines the HTTP response code specifications for MTPush REST API
MTPush Push API the new version of v4 API meets this specification
Status Code Definition
| Code | Description | Detailed Explanation |
|---|---|---|
| 200 | OK | Success! |
| 400 | Incorrect request | The request is invalid. The corresponding description will explain the reason. |
| 401 | Not verified | No verification information or verification failed |
| 403 | Rejected | The request is understood but not accepted. The corresponding description will explain the reason. |
| 404 | Unable to find | The resource does not exist, the requested user does not exist, and the request format is not supported. |
| 405 | The request method is not suitable. | This operation does not support requests from this method. |
| 410 | Offline | The requested resource is offline. Please refer to the relevant announcement. |
| 429 | Excessive requests | The number of requests exceeds the limit. The corresponding description will explain the specific reason. |
| 500 | Internal Service error | An internal error occurred on the server. Please contact us to resolve the problem as soon as possible. |
| 502 | Invalid proxy | The service server is offline or being upgraded. Please try again later. |
| 503 | The service is temporarily invalid. | The server cannot respond to the request. Please try again later. |
| 504 | Agent timeout | The server is running but cannot respond to the request. Please try again later. |
Compliance
- The correct code must be 200.
- Business logic error code, using 4xx or 400
- Server-side internal error code, using 5xx or 500
- When the business is abnormal，the returned content uses JSON format to define error information
