personal-limit-high-consumption
Restricted Consumption Personnel Lookup
Query whether an individual is on the restricted high-consumption list based on name, ID number, and mobile number, returning verification results and related record lists, suitable for risk control review and background checks.
Usage Cost
20 coins/call
Quick Start
Use a unified response envelope and call directly from your backend.
https://openapi.toolkk.com/v1/personal-limit-high-consumptioncURL Example
curl --request POST \
--url 'https://openapi.toolkk.com/v1/personal-limit-high-consumption' \
--header 'Content-Type: application/json' \
--header 'X-API-Key: YOUR_API_KEY' \
--data '{\n "name": "张三",\n "idcard_number": "110105199003078887",\n "mobile_number": "13800138000"\n}'Python Example
import os
import requests
url = "https://openapi.toolkk.com/v1/personal-limit-high-consumption"
payload = {
"name": "张三",
"idcard_number": "110105199003078887",
"mobile_number": "13800138000"
}
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/personal-limit-high-consumption"
payload := []byte("{\n \"name\": \"张三\",\n \"idcard_number\": \"110105199003078887\",\n \"mobile_number\": \"13800138000\"\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 \"name\": \"张三\",\n \"idcard_number\": \"110105199003078887\",\n \"mobile_number\": \"13800138000\"\n}";
HttpRequest request = HttpRequest.newBuilder()
.uri(URI.create("https://openapi.toolkk.com/v1/personal-limit-high-consumption"))
.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/personal-limit-high-consumption';
$payload = "{\n \"name\": \"张三\",\n \"idcard_number\": \"110105199003078887\",\n \"mobile_number\": \"13800138000\"\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": "SUCCESS",
"message": "success",
"data": {
"result": "未列入限制消费名单",
"total": 0,
"list": []
}
}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 |
|---|---|---|---|---|
| name | string | Unspecified | Unspecified | 张三 |
| idcard_number | string | Unspecified | Unspecified | 110105199003078887 |
| mobile_number | string | Unspecified | Unspecified | 13800138000 |
Request Example
{
"name": "张三",
"idcard_number": "110105199003078887",
"mobile_number": "13800138000"
}- 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 | SUCCESS |
| message | string | Unspecified | Unspecified | success |
| data | object | Unspecified | Unspecified | {...} |
| data.result | string | Unspecified | Unspecified | 未列入限制消费名单 |
| data.total | number | Unspecified | Unspecified | 0 |
| data.list | array | Unspecified | Unspecified | [] |
Response Example
{
"code": "SUCCESS",
"message": "success",
"data": {
"result": "未列入限制消费名单",
"total": 0,
"list": []
}
}$.code == 200 API overview
Capabilities, use cases, limitations, and frequently asked questions.
API Capabilities
The Restricted High-Consumption Personnel Query API allows enterprises to query whether an individual is listed on the restricted high-consumption (referred to as "restricted spending") personnel list by inputting their name, ID number, and mobile number. The API will return a clear verification result (e.g., whether they are on the list), along with the total number of related records and a detailed list. This API can provide auxiliary information for enterprise credit assessment, risk control, and background checks.
Request and Response
- Request Parameters: The
name(name),idcard_number(ID number), andmobile_number(mobile number) of the queried person must be provided simultaneously. Please ensure the input information is true, valid, and matching. - Return Results: In the returned
dataobject, theresultfield describes the current status (e.g., "Not listed on the restricted consumption list"),totalindicates the number of relevant records, and thelistarray contains specific restricted spending record details (if any). - Troubleshooting Failures: If the query fails or an error occurs, please check if the ID number format is valid and if the mobile number is a standard 11-digit number.