BINANCE SAPI · C2C

Update Ads API

Update and modify existing peer-to-peer (C2C) advertisement settings including pricing, transaction bounds, counterparty limits, auto-reply messages, and payment method bindings.

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

Overview

This endpoint modifies parameters for an existing C2C (P2P) advertisement identified by its unique advNo. Merchants and market-making bots can adjust offer prices, update total crypto liquidity reserves, alter minimum/maximum order limits, or modify buyer/seller eligibility filters on active listings.

Because changing core advertisement terms affects user asset commitments and security rules, requests require valid two-factor authentication (2FA) verification codes passed within the payload.

📖 See also: How to Change Ad Price on Binance Using Python: A Step-by-Step Guide

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).
advNo Body STRING Required Unique C2C advertisement number identifier to update.
price Body NUMBER Optional Updated unit offer price per crypto unit.
priceType Body INT Optional Pricing scheme: 1 Fixed Price, 2 Floating Price.
initAmount Body NUMBER Optional Updated total cryptocurrency liquidity amount allocated to the ad.
minSingleTransAmount Body NUMBER Optional Updated minimum fiat order transaction limit.
maxSingleTransAmount Body NUMBER Optional Updated maximum fiat order transaction limit.
tradeMethods Body ARRAY Optional Array of updated payment method objects bound to the ad.
updateMode Body STRING Optional Update mode flag specifying full or partial parameter updates.
authType Body STRING Optional Two-factor authentication method used (e.g., GOOGLE, SMS, FIDO2).
!
Authentication Requirements

Modifying active advertisement parameters requires passing valid 2FA verification tokens (e.g., googleVerifyCode) inside the JSON request body.

02

Request Example

Example POST request using cURL to update an advertisement price and limits.

cURL BASH
curl -X POST \
'https://api.binance.com/sapi/v1/c2c/ads/update' \
-H 'clientType: WEB' \
-H 'Content-Type: application/json' \
-d '{
  "advNo": "1122334455667788",
  "price": 1.03,
  "minSingleTransAmount": 100,
  "maxSingleTransAmount": 2000,
  "authType": "GOOGLE",
  "googleVerifyCode": "123456"
}'
03

Response

Example response returned on successful advertisement update.

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

Response Fields

Field Type Description
code STRING Standard Binance status code ("000000" indicates success).
message STRING Response execution feedback or error description.
data BOOLEAN Returns true if the advertisement update was successfully applied.
success BOOLEAN Indicates overall request status.
04

How It Works

Workflow for updating an existing C2C advertisement.

01 Specify Adv Number Identify target advNo to modify.
02 Set New Terms Pass updated prices, limits, or remarks payload.
03 Attach 2FA Code Include active 2FA verification token.
04 Apply Update Execute update request to reflect live changes on C2C market.

Common Use Cases

Dynamic Market Repricing

Reposition active advertisement offer prices dynamically as underlying crypto market rates shift.

Liquidity Rebalancing

Adjust allocated crypto inventory or order bounds without creating new advertisement listings.

Payment Channel Swapping

Update active bank accounts or settlement channels bound to the advertisement.



💬
Telegram WhatsApp