verify-mobile_twice_check
Recycled Phone Number Lookup
Provides a recycled phone number lookup API service, allowing developers to quickly check reissued mobile number data and integrate it into business systems.
Usage Cost
60 coins/call
Quick Start
Use a unified response envelope and call directly from your backend.
https://openapi.toolkk.com/v1/verify-mobile_twice_checkcURL Example
curl --request POST \
--url 'https://openapi.toolkk.com/v1/verify-mobile_twice_check' \
--header 'Content-Type: application/json' \
--header 'X-API-Key: YOUR_API_KEY' \
--data '{\n "phone_number": "13800138000",\n "date": "20240101"\n}'Python Example
import os
import requests
url = "https://openapi.toolkk.com/v1/verify-mobile_twice_check"
payload = {
"phone_number": "13800138000",
"date": "20240101"
}
headers = {
"Content-Type": "application/json",
"X-API-Key": os.getenv("TOOLKK_API_KEY", "YOUR_API_KEY"),
}
response = requests.request("POST", url, headers=headers, json=payload, timeout=30)
response.raise_for_status()
print(response.json())Go Example
package main
import (
"bytes"
"fmt"
"io"
"net/http"
)
func main() {
endpoint := "https://openapi.toolkk.com/v1/verify-mobile_twice_check"
payload := []byte("{\n \"phone_number\": \"13800138000\",\n \"date\": \"20240101\"\n}")
req, err := http.NewRequest("POST", endpoint, bytes.NewBuffer(payload))
if err != nil {
panic(err)
}
req.Header.Set("Content-Type", "application/json")
req.Header.Set("X-API-Key", "YOUR_API_KEY")
resp, err := http.DefaultClient.Do(req)
if err != nil {
panic(err)
}
defer resp.Body.Close()
body, err := io.ReadAll(resp.Body)
if err != nil {
panic(err)
}
fmt.Println(string(body))
}Java Example
import java.net.URI;
import java.net.http.HttpClient;
import java.net.http.HttpRequest;
import java.net.http.HttpResponse;
public class ToolkkExample {
public static void main(String[] args) throws Exception {
String payload = "{\n \"phone_number\": \"13800138000\",\n \"date\": \"20240101\"\n}";
HttpRequest request = HttpRequest.newBuilder()
.uri(URI.create("https://openapi.toolkk.com/v1/verify-mobile_twice_check"))
.method("POST", HttpRequest.BodyPublishers.ofString(payload))
.header("Content-Type", "application/json")
.header("X-API-Key", "YOUR_API_KEY")
.build();
HttpResponse<String> response = HttpClient.newHttpClient()
.send(request, HttpResponse.BodyHandlers.ofString());
System.out.println(response.body());
}
}PHP Example
<?php
$endpoint = 'https://openapi.toolkk.com/v1/verify-mobile_twice_check';
$payload = "{\n \"phone_number\": \"13800138000\",\n \"date\": \"20240101\"\n}";
$ch = curl_init($endpoint);
curl_setopt_array($ch, [
CURLOPT_RETURNTRANSFER => true,
CURLOPT_CUSTOMREQUEST => 'POST',
CURLOPT_HTTPHEADER => [
'Content-Type: application/json',
'X-API-Key: YOUR_API_KEY',
],
CURLOPT_POSTFIELDS => $payload,
]);
$response = curl_exec($ch);
if ($response === false) {
throw new RuntimeException(curl_error($ch));
}
curl_close($ch);
echo $response;Response Example
{
"code": "200",
"message": "success",
"data": {
"result_code": "0000",
"result_msg": "调用成功",
"desc": "不是二次卡",
"result": 1,
"operator": "cucc"
}
}Examples illustrate the response structure. Actual results depend on the API response.
- Authentication
- Send X-API-Key in request headers
- Rate limit
- 600 req/min
- Timeout
- 5000 ms
Send your API Key in the X-API-Key header from your backend.
Check both HTTP status and business fields before treating a call as successful.
Use retries and backoff together with rate limits in high-frequency scenarios.
Request Fields
Send requests from your server with the key in the X-API-Key header.
Request Fields
The fields below are derived from example JSON for integration reference only.
| Path | Type | Required | Description | Sample |
|---|---|---|---|---|
| phone_number | string | Unspecified | Unspecified | 13800138000 |
| date | string | Unspecified | Unspecified | 20240101 |
Request Example
{
"phone_number": "13800138000",
"date": "20240101"
}- Authentication
- Send X-API-Key in request headers
- Rate limit
- 600 req/min
- Timeout
- 5000 ms
Response Fields
Examples illustrate the response structure. Actual results depend on the API response.
Response Fields
The fields below are derived from example JSON for integration reference only.
| Path | Type | Required | Description | Sample |
|---|---|---|---|---|
| code | string | Unspecified | Unspecified | 200 |
| message | string | Unspecified | Unspecified | success |
| data | object | Unspecified | Unspecified | {...} |
| data.result_code | string | Unspecified | Unspecified | 0000 |
| data.result_msg | string | Unspecified | Unspecified | 调用成功 |
| data.desc | string | Unspecified | Unspecified | 不是二次卡 |
| data.result | number | Unspecified | Unspecified | 1 |
| data.operator | string | Unspecified | Unspecified | cucc |
Response Example
{
"code": "200",
"message": "success",
"data": {
"result_code": "0000",
"result_msg": "调用成功",
"desc": "不是二次卡",
"result": 1,
"operator": "cucc"
}
}$.result_code == '0000'API overview
Capabilities, use cases, limitations, and frequently asked questions.
Recycled Phone Number Lookup API Overview
The Recycled Phone Number Lookup API helps developers quickly process recycled (reissued) mobile number queries within their systems. It returns structured results and is ideal for business integration, automated API calls, and system docking.
Use Cases
- Integrate recycled phone number lookup capabilities into internal systems, SaaS platforms, automated workflows, or operational backends.
- Suitable for business scenarios requiring stable API calls, standardized responses, and orchestratable interface capabilities.
- Recommended to combine with request rate limiting, failure retries, and result caching strategies to improve overall integration stability.
Integration Recommendations
- Verify request parameter formats, authentication methods, and error code handling logic before integration.
- For high-frequency query scenarios, it is recommended to implement log tracking, timeout controls, and idempotency handling.
- If the results are used for risk control or automated decision-making, we recommend combining them with business rules for secondary validation rather than relying solely on the API response.