BINANCE SAPI · C2C

Update Ads Status API

Batch update the operational status of multiple peer-to-peer (C2C) advertisements simultaneously, allowing merchants to publish, pause, or take down ads in bulk.

ENDPOINT

POST /sapi/v1/c2c/ads/updateStatus

Authentication USER_DATA / SIGNED

API Group C2C / Ads

Method POST

Response JSON

Overview

This endpoint executes batch status updates across multiple C2C (P2P) advertisements in a single request. Merchants and automated trading bots use this operation to quickly toggle advertisement visibility—such as publishing offline ads online, pausing active ads during non-working hours, or closing completed listings.

By supporting array inputs (`advNos`), developers can control entire portfolios of peer-to-peer offer listings simultaneously without making repetitive single-item API calls.

Request Parameters

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`).
`advNos`	Body	ARRAY	Required	Array of target C2C advertisement number strings to update.
`advStatus`	Body	INT	Required	Target status code: `1` Published / Online, `2` Paused / Offline, `3` Closed / Deleted.
`x-gray-env`	Header	STRING	Optional	Environment flag identifier used for stage testing.
`x-trace-id`	Header	STRING	Optional	Custom client trace ID for request tracking.
`x-user-id`	Header	STRING	Optional	Target user identifier for user-specific ad checks.

Batch Processing Performance

Using batch updates minimizes network latency and rate limit usage compared to updating ads individually. Always inspect the returned failedList array to confirm if any specific ad number failed to update.

Request Example

Example POST request using cURL to pause multiple advertisements.

cURL BASH

curl -X POST \
'https://api.binance.com/sapi/v1/c2c/ads/updateStatus' \
-H 'clientType: WEB' \
-H 'Content-Type: application/json' \
-d '{
  "advNos": [
    "1122334455667788",
    "9988776655443322"
  ],
  "advStatus": 2
}'

Response

Example response returned on batch status update execution.

RESPONSE 200 OK

{
    "code": "000000",
    "message": "success",
    "data": {
        "successList": [
            "1122334455667788",
            "9988776655443322"
        ],
        "failedList": []
    },
    "success": true
}

Response Fields

Field	Type	Description
`code`	STRING	Standard Binance status code (`"000000"` indicates success).
`data.successList`	ARRAY	Array of advertisement number strings that successfully transitioned to the target status.
`data.failedList`	ARRAY	Array of advertisement number strings that failed to update.
`success`	BOOLEAN	Indicates overall request execution state.

How It Works

Workflow for batch updating C2C advertisement status.

01 Select Ad Array Collect target advNos for status update.

02 Set Target Status Choose status code (1: Online, 2: Offline, 3: Closed).

03 Send Batch Request POST payload to /sapi/v1/c2c/ads/updateStatus.

04 Verify Results Confirm successful IDs in successList.

Common Use Cases

Emergency Kill-Switch

Instantly take all active merchant advertisements offline during extreme crypto market volatility or banking outages.

Schedule-Based Toggling

Automatically publish ads at the start of business hours and pause them overnight using scheduled server cron jobs.

Bulk Ad Cleanup

Batch close outdated or exhausted advertisement listings with a single API call.