Application Process
To use Mobile Number Status Query API, first open the Ace Data Cloud Console and copy your API Token.
If you are not logged in, you will be redirected to sign in and brought back to this page automatically.
A single API Token works across every service on the platform — no need to subscribe per service. New accounts receive free starter credit; when it runs low you can top up your shared balance in the console.
📘 Full documentation: Mobile Number Status Query API →
Basic Usage
First, understand the basic usage method, which is to input the mobile number to obtain the processed result. You need to simply pass amobile field. We can then fill in the corresponding content on the interface, as shown in the image:

accept: the format of the response result you want to receive, filled in asapplication/json, which is in JSON format.authorization: the key to call the API, which can be directly selected after application.
mobile: the mobile number to be processed, which is a required parameter.encryption: optional, sensitive field encryption parameter (if you need to send encrypted data).

result, the authentication result code, with the charging situation as follows.- Charging result codes:
- 0: Success
- Non-charging result codes:
- -1: No results found
- -2: Mobile number format is incorrect
- -3: Verification center service is busy
- Charging result codes:
description, business result description.status_code, status code:- 0: Normal
- 1: Suspended
- 2: Canceled
- 3: Invalid number
- 4: Not in the network
- 99: Unknown status
Error Handling
When calling the API, if an error occurs, the API will return the corresponding error code and message. For example:400 token_mismatched: Bad request, possibly due to missing or invalid parameters.400 api_not_implemented: Bad request, possibly due to missing or invalid parameters.401 invalid_token: Unauthorized, invalid or missing authorization token.429 too_many_requests: Too many requests, you have exceeded the rate limit.500 api_error: Internal server error, something went wrong on the server.

