BINANCE SAPI · C2C

Post An Ad API

Create and publish new peer-to-peer (C2C) buy or sell advertisements with custom pricing models, order limits, payment method bindings, and strict counterparty eligibility filters.

ENDPOINT
POST /sapi/v1/c2c/ads/post
Authentication USER_DATA / 2FA SIGNED
API Group C2C / Ads
Method POST
Response JSON

Overview

This endpoint submits and publishes a new C2C (P2P) advertisement on Binance. Merchants and market-making bots can configure fixed or floating price formulas, initial asset liquidity amounts, trade execution limits, auto-reply messages, and supported local payment methods.

To manage counterparty risk, the endpoint supports extensive risk control options such as minimum completed order counts, completion rate thresholds, account age restrictions, and required KYC levels for taking users.

01

Request Parameters

Key parameters accepted in Body and HTTP Headers.

Parameter In Type Required Description
clientType Header STRING Required Client Device Type initiating the request (e.g., WEB, APP).
asset Body STRING Required Cryptocurrency asset symbol to trade (e.g., USDT, BTC).
fiatUnit Body STRING Required Target fiat currency symbol (e.g., USD, EUR, UAH).
tradeType Body STRING Required Advertisement trade side: BUY or SELL.
priceType Body INT Required Pricing scheme: 1 Fixed Price, 2 Floating Price.
price Body NUMBER Required Fixed offer price per unit when priceType=1.
initAmount Body NUMBER Required Total cryptocurrency amount allocated to publish on the ad.
minSingleTransAmount Body NUMBER Required Minimum fiat transaction limit per single order.
maxSingleTransAmount Body NUMBER Required Maximum fiat transaction limit per single order.
tradeMethods Body ARRAY Required List of payment method objects containing payType and payId.
onlineNow Body BOOLEAN Optional Set to true to immediately publish the ad online upon creation.
authType Body STRING Optional Two-factor authentication method used (e.g., GOOGLE, SMS, FIDO2).
!
Two-Factor Authentication (2FA) Security

Publishing C2C advertisements requires valid two-factor verification codes (such as googleVerifyCode or mobileVerifyCode) passed inside the request body payload.

02

Request Example

Example POST request using cURL to publish a fixed-price USDT ad.

cURL BASH
curl -X POST \
'https://api.binance.com/sapi/v1/c2c/ads/post' \
-H 'clientType: WEB' \
-H 'Content-Type: application/json' \
-d '{
  "asset": "USDT",
  "fiatUnit": "USD",
  "tradeType": "SELL",
  "priceType": 1,
  "price": 1.02,
  "initAmount": 1000,
  "minSingleTransAmount": 50,
  "maxSingleTransAmount": 1000,
  "onlineNow": true,
  "tradeMethods": [
    {
      "payType": "BANK_TRANSFER",
      "payId": 123456
    }
  ],
  "authType": "GOOGLE",
  "googleVerifyCode": "123456"
}'
03

Response

Example response returned on successful advertisement creation.

RESPONSE 200 OK
{
    "code": "000000",
    "message": "success",
    "data": "1122334455667788",
    "success": true
}

Response Fields

Field Type Description
code STRING Standard status response code ("000000" indicates success).
message STRING Response execution feedback or error details.
data STRING Newly generated unique advertisement number string (adsNo).
success BOOLEAN Indicates overall request execution result.
04

How It Works

Workflow for creating and launching a C2C advertisement.

01 Configure Offer Set asset, fiat, pricing model, and total liquidity amount.
02 Bind Payments Select active bank or payment method identifiers.
03 Set Risk Rules Define counterparty completion rate and age filters.
04 Verify & Publish Pass 2FA authentication and launch ad to C2C market.

Common Use Cases

Automated Ad Creation

Programmatically post new buy/sell offers with dynamic pricing formulas as market conditions shift.

Merchant Liquidity Provision

Publish tailored P2P liquidity ads bound to specific high-volume local payment channels.

Counterparty Filtering

Automatically enforce buyer/seller qualification checks to mitigate fraud and optimize order completion rates.



💬
Telegram WhatsApp