Binance API / SAPI / C2C
BINANCE SAPI · C2C

Get Ad Details By Merchant Number API

Query advertisement details and merchant-specific offer configurations for peer-to-peer (C2C) trading using a designated merchant identifier.

ENDPOINT
GET /sapi/v1/c2c/merchant/getAdDetails
Authentication NONE (PUBLIC)
API Group C2C / Merchant
Method GET
Response JSON

Overview

This endpoint fetches peer-to-peer advertisement details associated with a specific merchant profile via their unique merchant number (`merchantNo`). It enables client apps, trading bots, and merchant management dashboards to inspect active advertisements, bound payment channels, and transaction terms directly tied to a merchant account.

Because this request is executed over HTTP GET and does not require private cryptographic signatures, it is ideal for public storefront lookups, merchant profile rendering, and competitor ad tracking.

01

Request Parameters

Parameters accepted in Query string and HTTP Headers.

ParameterInTypeRequiredDescription
clientTypeHeaderSTRINGRequiredClient Device Type initiating the request (e.g., WEB, APP, WEB_MOBILE).
merchantNoQuerySTRINGOptionalUnique merchant identifier number to query ads for.
x-gray-envHeaderSTRINGOptionalEnvironment flag identifier used for internal gray/stage testing.
x-trace-idHeaderSTRINGOptionalCustom client trace ID for request lifecycle tracking and debugging.
x-user-idHeaderSTRINGOptionalTarget user identifier for context-specific queries.
i

HTTP GET Query Request

Pass the merchantNo as a URL query parameter (e.g., ?merchantNo=M12345678) alongside the mandatory clientType header in the HTTP request.

02

Request Example

Example GET request using cURL.

cURL BASH
curl -X GET \
'https://api.binance.com/sapi/v1/c2c/merchant/getAdDetails?merchantNo=M12345678' \
-H 'clientType: WEB'

03

Response

Example response returned on successful request execution.

RESPONSE 200 OK
{
    "code": "000000",
    "message": "success",
    "data": {
        "merchantNo": "M12345678",
        "nickName": "FastMerchant",
        "adsDetailList": [
            {
                "advNo": "1122334455667788",
                "asset": "USDT",
                "fiatUnit": "USD",
                "tradeType": "SELL",
                "price": "1.01",
                "surplusAmount": "2500.00",
                "minSingleTransAmount": "50.00",
                "maxSingleTransAmount": "1000.00",
                "advStatus": 1
            }
        ]
    },
    "success": true
}

Response Fields

FieldTypeDescription
codeSTRINGStandard Binance status code ("000000" indicates success).
messageSTRINGStatus description or response feedback message.
data.merchantNoSTRINGIdentifier of the requested merchant profile.
data.nickNameSTRINGPublic display nickname of the merchant.
data.adsDetailListARRAYList of active advertisement objects managed by the specified merchant.
successBOOLEANIndicates overall request execution result.

04

How It Works

Workflow for querying merchant ad details.

01 Set Merchant No Attach target merchantNo to URL query parameters.
 
02 Send GET Request Call /sapi/v1/c2c/merchant/getAdDetails endpoint.
 
03 Parse Ad List Extract ad numbers, price terms, and available amounts.
 
04 Display Storefront Render merchant-specific listings on UI or bot tracking monitors.

Common Use Cases

Merchant Storefront UI

Render dedicated merchant profile pages displaying all active buy/sell ads currently offered by the merchant.

Competitor Monitoring

Track competitor pricing models, available liquidity limits, and trade bounds in real time.

Ad Portfolio Verification

Verify published advertisement details and order parameters directly associated with a merchant number.

💬
Telegram WhatsApp