cp.queryKYC
This interface is implemented by the platform application (APP) server and called by the SUD OpenPaaS server.
Query developer/vendor subject KYC. In the reference implementation, subject-level fields match GET /developer/info; richer filing subject/manager fields are in game.queryICP (subject_info / subject_manager).
Invocation method:
- HTTPS call
HTTPS Call
http
POST {query_cp_kyc_webhook}Request Parameters - Header
| Property | Type | Default | Required | Description |
|---|---|---|---|---|
| Authorization | string | Yes | Format: Bearer {access_token}; subject ID from token |
Request Parameters - Body
Send an empty JSON object {}.
| Property | Type | Default | Required | Description |
|---|---|---|---|---|
| (none) | object | {} | Yes | Empty JSON {} |
Return Value
Object
Returned JSON packet
| Property | Type | Description |
|---|---|---|
| ret_code | integer | 0 success, non-zero failure |
| ret_msg | string | "success" or error reason |
| data | object | Business body (when ret_code=0) |
| data.id | string | Third-party subject ID |
| data.subject_name | string | Subject name |
| data.subject_type | integer | 0 individual, 1 enterprise |
| data.uscc | string | Unified social credit code (enterprise) |
| data.username | string | Login username |
| data.status | integer | 0 disabled, 1 enabled |
| timestamp | long | Millisecond timestamp |
Valid values of ret_code
| Value | Description | Min version |
|---|---|---|
| 0 | Success | |
| 40001 | invalid access_token | |
| 40002 | cp not found |
cURL Request
bash
curl -X POST \
{query_cp_kyc_webhook} \
-H 'Authorization: Bearer {access_token}' \
-H 'Content-Type: application/json; charset=utf-8' \
-d '{}'Success Response
json
{
"ret_code": 0,
"ret_msg": "success",
"data": {
"id": "a1000000000000000000000000000001",
"subject_name": "Example Tech Co., Ltd.",
"subject_type": 1,
"uscc": "91110000MA01234567",
"username": "demo_dev",
"status": 1
},
"timestamp": 1719820800000
}Error Response
json
{
"ret_code": 40001,
"ret_msg": "invalid access_token"
}