BINANCE SAPI · C2C

Get User Detail API

Query the authenticated user's C2C (P2P) base profile attributes, including account nickname, user number, KYC verification level, and merchant privileges.

ENDPOINT

POST /sapi/v1/c2c/user/baseDetail

Authentication USER_DATA / SIGNED

API Group C2C / User Profile

Method POST

Response JSON

Overview

This endpoint provides core account profile information for the authenticated Binance P2P user. It returns critical user metadata such as the public nickname, user number (`userNo`), email/SMS verification flags, KYC certification tier, and merchant status.

Automated trading systems and merchant management daemons execute this endpoint during bot startup to confirm account permissions and verify operational capabilities before initiating trading sessions.

Request Parameters

Header parameters accepted by the endpoint.

Header	Type	Required	Description
`clientType`	STRING	Required	Client Device Type initiating the request (e.g., `WEB`, `APP`, `WEB_MOBILE`).
`x-gray-env`	STRING	Optional	Environment flag identifier used for internal gray/stage testing.
`x-trace-id`	STRING	Optional	Custom client trace ID for request lifecycle tracking and debugging.
`x-user-id`	STRING	Optional	Target user identifier for context validation.

HTTP POST with Empty Body

No JSON payload body is required for this call. Simply supply the mandatory clientType header inside the HTTP Request Headers.

Request Example

Example POST request using cURL to fetch user profile details.

cURL BASH

curl -X POST \
'https://api.binance.com/sapi/v1/c2c/user/baseDetail' \
-H 'clientType: WEB'

Response

Example response returned on successful query execution.

RESPONSE 200 OK

{
    "code": "000000",
    "message": "success",
    "data": {
        "userNo": "s1234567890abcdef",
        "nickName": "MerchantAlpha",
        "email": "user@example.com",
        "mobile": "+1234567890",
        "kycStatus": 1,
        "kycLevel": "VERIFIED_PLUS",
        "isMerchant": true,
        "merchantLevel": 2,
        "userStatus": 1
    },
    "success": true
}

Response Fields

Field	Type	Description
`code`	STRING	Standard Binance status code (`"000000"` indicates success).
`data.userNo`	STRING	Unique internal user identifier on Binance P2P.
`data.nickName`	STRING	Public display nickname on the C2C trading platform.
`data.kycStatus`	INT	Identity verification status flag (`1` indicates verified).
`data.kycLevel`	STRING	KYC tier certification level (e.g., `VERIFIED`, `VERIFIED_PLUS`).
`data.isMerchant`	BOOLEAN	Indicates whether the account has active Binance P2P merchant privileges.
`data.merchantLevel`	INT	Merchant tier ranking (e.g., `1`: Verified Merchant, `2`: VIP Merchant).
`data.userStatus`	INT	Overall account trading status flag (`1`: Normal / Active).
`success`	BOOLEAN	Indicates overall request execution result.

How It Works

Workflow for retrieving account profile attributes.

01 Set Headers Pass clientType in HTTP request headers.

02 Send POST Request Query /sapi/v1/c2c/user/baseDetail endpoint.

03 Verify Privileges Confirm KYC tier level and merchant status.

04 Initialize Bots Authorize trading routines or render account profile UI.

Common Use Cases

Bot Pre-Flight Verification

Verify KYC tier requirements and active merchant flags automatically before launching automated ad repricers.

Account Dashboard Profile

Display account verification tiers, nicknames, and merchant level badges inside custom administrative interfaces.

Multi-Account Management

Audit operational permissions and verified identity attributes across multiple API keys and account instances.