BINANCE SAPI · C2C

Check If Can Place Order API

Pre-validate user eligibility, counterparty trading conditions, and advertisement state before initiating a peer-to-peer (C2C) trade order.

ENDPOINT

POST /sapi/v1/c2c/orderMatch/checkIfCanPlaceOrder

Authentication USER_DATA / SIGNED

API Group C2C / Order Match

Method POST

Response JSON

Overview

This endpoint checks whether an authenticated user meets all conditions to place an order against a specific peer-to-peer advertisement (`adOrderNo`). It verifies KYC tier requirements, country restrictions, trade completion rates, account age filters, and ad liquidity limits established by the ad creator.

Automated trading systems, mobile clients, and web dashboards execute this pre-flight verification to prevent failed order creation attempts and improve checkout conversion rates.

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`, `WEB_MOBILE`).
`adOrderNo`	Body	STRING	Required	Unique advertisement order identifier to test eligibility against.
`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.

Pre-Order Verification Best Practice

Run this verification whenever a user selects an advertisement or right before submitting a trade order to ensure the ad is still active and the user satisfies all trading limits.

Request Example

Example POST request using cURL to check order placement eligibility.

cURL BASH

curl -X POST \
'https://api.binance.com/sapi/v1/c2c/orderMatch/checkIfCanPlaceOrder' \
-H 'clientType: WEB' \
-H 'Content-Type: application/json' \
-d '{
  "adOrderNo": "112233445566778899"
}'

Response

Example response returned on successful verification.

RESPONSE 200 OK

{
    "code": "000000",
    "message": "success",
    "data": true,
    "success": true
}

Response Fields

Field	Type	Description
`code`	STRING	Standard Binance status response code (`"000000"` indicates success).
`message`	STRING	Response execution feedback or status description.
`data`	BOOLEAN	Returns `true` if the user is allowed to place an order on this ad; returns `false` otherwise.
`success`	BOOLEAN	Indicates overall request execution result.

How It Works

Workflow for validating order placement eligibility.

01 Target Ad Select target advertisement number (adOrderNo).

02 Send Verification POST payload to /checkIfCanPlaceOrder.

03 Validate Rules Check KYC, completion rate, and ad balance status.

04 Proceed with Trade Open trade form or execute auto-buy order.

Common Use Cases

Pre-Trade UI Validation

Enable or disable "Buy / Sell" action buttons dynamically across P2P ad listing tables.

Arbitrage Bot Optimization

Quickly eliminate restricted or incompatible advertisements before attempting automated trade execution.

Requirement Pre-Checks

Verify counterparty filter compliance (e.g. minimum completed orders, registered days) in advance.

← Previous Endpoint Check If Can Release Digital Asset API Next Endpoint → Check If Allowed Cancel Order API

Related Binance API Endpoints

📚

Part of the Spot Arbitrage Guide

This article is part of our complete learning guide covering professional cross-exchange cryptocurrency arbitrage.

Explore the Spot Arbitrage Guide →

📚

Part of the Binance P2P Automation 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 →

Novelty