Retrieve historical trading statistics, trade completion rates, and average release times for the counterparty involved in a specific peer-to-peer (C2C) order.
/sapi/v1/c2c/orderMatch/queryCounterPartyOrderStatistic
This endpoint enables a buyer, seller, or automated risk system to inspect the historical performance profile of the specific counterparty attached to an active or completed C2C (P2P) order. It supplies crucial counterparty trust metrics, including completed order totals, 30-day order counts, average payment duration, and historical finish rates.
Automated trading desks and risk management daemons invoke this endpoint immediately upon order creation to evaluate counterparty reliability before executing fiat payouts or releasing crypto assets.
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, WEB_MOBILE).
|
orderNumber |
Body | STRING | Required | Unique order number identifier to inspect the counterparty for. |
x-gray-env |
Header | STRING | Optional | Environment flag identifier used for internal gray/stage testing. |
x-trace-id |
Header | STRING | Optional | Custom client trace ID for request lifecycle tracking and debugging. |
x-user-id |
Header | STRING | Optional | Target user identifier for context validation. |
Query counterparty statistics immediately following order placement (placeOrder) to dynamically flag low-completion or high-risk trading accounts prior to processing payment settlement.
Example POST request using cURL to query counterparty statistics.
curl -X POST \
'https://api.binance.com/sapi/v1/c2c/orderMatch/queryCounterPartyOrderStatistic' \
-H 'clientType: WEB' \
-H 'Content-Type: application/json' \
-d '{
"orderNumber": "202608161234567890"
}'
Example response returned on successful query execution.
{
"code": "000000",
"message": "success",
"data": {
"completedOrderNum": 620,
"finishRate": 0.994,
"avgPayTime": 140,
"avgReleaseTime": 95,
"monthOrderCount": 180,
"monthFinishRate": 0.991,
"registeredDays": 410
},
"success": true
}
| Field | Type | Description |
|---|---|---|
code |
STRING |
Standard Binance status code ("000000" indicates success).
|
message |
STRING | Status description or response feedback message. |
data.completedOrderNum |
INT | Lifetime total count of successfully executed orders by the counterparty. |
data.finishRate |
DOUBLE | All-time historical trade completion rate percentage ratio. |
data.avgPayTime |
INT | Average fiat payment confirmation duration in seconds. |
data.avgReleaseTime |
INT | Average digital asset release duration in seconds. |
data.monthOrderCount |
INT | Total completed orders executed by the counterparty in the rolling 30-day window. |
data.monthFinishRate |
DOUBLE | Completion rate percentage achieved over the rolling 30-day window. |
data.registeredDays |
INT | Total number of days since the counterparty registered on the exchange. |
success |
BOOLEAN | Indicates overall request execution result. |
Workflow for querying counterparty trading history.
Hold or reject automated payouts if the counterparty's completion rate falls below safety thresholds (e.g. < 90%).
Check registeredDays to apply extra verification checks on newly created accounts before processing large-volume orders.
Render counterparty trust badges and trading speed indicators inside merchant chat and management consoles.
This article is part of our complete learning guide covering professional cross-exchange cryptocurrency arbitrage.
Explore the Spot Arbitrage Guide →This article is part of our complete learning guide covering Binance P2P automation, merchant tools, and automated trading.
Explore the Binance P2P Automation Guide →