How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Binance Trading API

Trading endpoints for COIN-M futures orders.

Binance Trading API is one of 28 APIs that Binance publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

Tagged areas include Trading. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an AsyncAPI specification.

This API exposes 29 operations across 18 paths, and defines 10 schemas. It is described by OpenAPI 3.1.0, at version 1.

Requests are made against a single base URL, https://api.binance.com.

29 operations 18 paths 10 schemas 6 DELETE11 GET12 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1
Base URL
https://api.binance.com
Authentication
API Key, API Key
Terms of Service
Resource Areas
1

Authentication & Security 2

Binance Trading API declares 2 security schemes for authenticating requests. An API key is passed in the header as X-MBX-APIKEY (apiKey). An API key is passed in the query as signature (hmacSignature). By default, every request must be authenticated.

Paths & Operations 29

Across 18 paths, the API surfaces 29 operations — 6 DELETE, 11 GET, 12 POST. Each is listed below with its method, path, parameters, and response codes.

Trading 29

Trading endpoints for COIN-M futures orders.

POST
/dapi/v1/order
New order
createOrder 17 params → 200400
GET
/dapi/v1/order
Query order
getOrder 6 params → 200
DELETE
/dapi/v1/order
Cancel order
cancelOrder 6 params → 200
GET
/dapi/v1/openOrders
Current all open orders
getOpenOrders 4 params → 200
POST
/eapi/v1/order
New order
createOrder 14 params → 200400
GET
/eapi/v1/order
Query single order
getOrder 6 params → 200
DELETE
/eapi/v1/order
Cancel order
cancelOrder 6 params → 200
GET
/eapi/v1/openOrders
Query current open orders
getOpenOrders 4 params → 200
POST
/sapi/v1/margin/order
Margin account new order
createMarginOrder 15 params → 200
GET
/sapi/v1/margin/order
Query margin account order
getMarginOrder 7 params → 200
DELETE
/sapi/v1/margin/order
Cancel margin account order
cancelMarginOrder 7 params → 200
GET
/sapi/v1/margin/openOrders
Query margin account open orders
getMarginOpenOrders 5 params → 200
POST
/papi/v1/um/order
New UM order
createUmOrder 9 params → 200
POST
/papi/v1/cm/order
New CM order
createCmOrder 9 params → 200
POST
/papi/v1/margin/order
New margin order
createMarginOrder 9 params → 200
POST
/api/v3/order
New order
createOrder 18 params → 200400401
GET
/api/v3/order
Query order
getOrder 6 params → 200400404
DELETE
/api/v3/order
Cancel order
cancelOrder 8 params → 200400
GET
/api/v3/openOrders
Current open orders
getOpenOrders 4 params → 200
DELETE
/api/v3/openOrders
Cancel all open orders on a symbol
cancelAllOpenOrders 4 params → 200
GET
/api/v3/allOrders
All orders
getAllOrders 8 params → 200
POST
/api/v3/order/oco
New OCO order
createOcoOrder 14 params → 200400
POST
/api/v3/order/test
Test new order
testNewOrder 9 params → 200
POST
/api/v3/sor/order
New order using SOR
createSorOrder 11 params → 200
POST
/fapi/v1/order
New order
createOrder 19 params → 200400
GET
/fapi/v1/order
Query order
getOrder 6 params → 200
DELETE
/fapi/v1/order
Cancel order
cancelOrder 6 params → 200
POST
/fapi/v1/batchOrders
Place multiple orders
createBatchOrders 4 params → 200
GET
/fapi/v1/openOrders
Current all open orders
getOpenOrders 4 params → 200

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are FuturesOrderResponse (23 properties), FuturesOrder (23 properties), Order (20 properties), OrderResponse (16 properties). Each schema is shown below with its type and property counts.

CancelOrderResponse
object
15 properties
Error_2
object
2 properties
Fill
object
5 properties
OcoOrderResponse
object
9 properties
Order
object
20 properties
FuturesOrderResponse
object
23 properties
Error
object
2 properties
FuturesOrder
object
23 properties
Error_3
object
2 properties
OrderResponse
object
16 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

binance-trading-api-openapi.yml Raw ↑

Other APIs Binance publishes across the network.

Binance Spot WebSocket API
Binance Spot WebSocket Streams
Binance Account API
Binance Assets API
Binance Auto-Invest API
Binance Borrow/Repay API
Binance Convert API
Binance Copy Trading API
Binance Crypto Loan API
Binance Deposits API
Binance Fiat API
Binance Flexible Products API
Where this information came from

This is an independent, third-party profile of Binance Trading API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.