HTTP **Status Code** | WebPush

HTTP Status Code

Last updated：12 days ago

This topic defines the HTTP response code specifications for MTPush REST API

MTPush Push API the new version of v4 API meets this specification

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.

HTTP 200 means the request was processed; it does not guarantee that every batch-push target succeeded. Check each results[target].success and read that item’s error.code on failure.
Request-level business errors use the corresponding 4xx status. Rate limiting of the entire batch request returns HTTP 400; an item-level rate-limit error 23008 can appear in an HTTP 200 response body.
Request-level internal server errors use the corresponding 5xx status, or 500.
When the business is abnormal，the returned content uses JSON format to define error information

HTTP Status Code