Binance Public Spot API

Name: Binance Public Spot API API
Brand: Binance Public Spot API
Availability: InStock

✓ Official Vendor SpecFinanceBankingapiKey340 EndpointsREST

For Agents

Place spot and margin trades, pull market data, manage Binance accounts and sub-accounts, and access savings, futures lookups, NFT, and Binance Pay across 340 endpoints.

Quickstart

Get started with Binance Public Spot API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"place a Binance spot order"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Binance Public Spot API API.

Place, query, and cancel spot orders including OCO, OTO, and SOR-routed order lists

Stream live market data via klines, depth, trades, and 24-hour ticker endpoints

Borrow, repay, and manage cross and isolated margin positions and account state

Manage sub-accounts and inter-account transfers from a parent account

GET STARTED

Start building with Binance Public Spot API API

Explore with Jentic

View OpenAPI Document

The Binance Public Spot API is the programmatic interface to Binance's spot exchange, exposing 340 endpoints covering market data, spot trading, margin, sub-accounts, savings, futures-related lookups, fiat on-ramps, C2C, NFT, and Binance Pay. It supports the standard exchange order lifecycle — place, query, cancel, list — with order types including market, limit, OCO, OTO, and SOR-routed orders, plus margin borrow and repay, isolated and cross margin, and account information lookups. Authentication is by API key in the X-MBX-APIKEY header for trading and account endpoints, with HMAC-SHA256 request signing required for signed endpoints.

Use Cases

Patterns agents use Binance Public Spot API API for, with concrete tasks.

★ Algorithmic Spot Trading

Quant teams and trading bots place and manage spot orders programmatically. The Binance API exposes POST /api/v3/order for new orders, DELETE /api/v3/order for cancels, GET /api/v3/openOrders for live state, and OCO and SOR variants for advanced strategies. Combined with /api/v3/klines and /api/v3/depth for market data, it covers a full algorithmic loop. Initial integration including HMAC signing and websocket user-data streams typically takes one to two weeks.

Place a LIMIT BUY order on BTCUSDT for 0.01 BTC at 60000 USDT via POST /api/v3/order, then poll GET /api/v3/order to confirm fill status.

Margin Trading and Leverage

Traders running cross-margin or isolated-margin strategies need borrow, repay, and order endpoints in one place. Binance exposes POST /sapi/v1/margin/borrow-repay for borrowing, POST /sapi/v1/margin/order for margin orders, and /sapi/v1/margin/account or /sapi/v1/margin/isolated/account for state. This avoids stitching together multiple platforms when running leveraged strategies. Setup typically takes a week beyond a working spot integration.

Borrow 1000 USDT on cross margin via POST /sapi/v1/margin/borrow-repay with type=BORROW, then place a leveraged BUY order via POST /sapi/v1/margin/order on BTCUSDT.

Treasury and Sub-Account Management

Funds and operations teams use Binance sub-accounts to segregate strategies and managed accounts. The API exposes the sub-account management surface and wallet endpoints to move assets between the parent and sub-accounts and to pull capital-flow history for reporting. Setup is typically three to five days for treasury-grade reconciliation.

Pull cross-margin capital flow via GET /sapi/v1/margin/capital-flow for the last seven days and reconcile against the local treasury ledger.

Market Data Pipelines for Research

Research teams need historical and live market data across many symbols. Binance exposes /api/v3/klines, /api/v3/aggTrades, /api/v3/historicalTrades, and /api/v3/exchangeInfo for symbol and rule discovery. These endpoints are public and unsigned, so a backfill pipeline can be built without API-key plumbing. Setup is typically one to two days for a single data feed.

For BTCUSDT, fetch one year of 1d klines via repeated GET /api/v3/klines calls and write each batch to local storage for backtesting.

AI Agent Trading and Reporting Assistant via Jentic

An AI assistant can place orders, monitor positions, and produce P&L reports from natural-language requests routed through Jentic. The X-MBX-APIKEY and HMAC secret are held in the Jentic vault, so the agent never sees the raw credentials, and Jentic returns the right Binance operation when the user asks something like "sell 0.5 BTC at market". Setup through Jentic is under an hour, versus over a week for a direct integration.

Search Jentic for 'place a Binance spot order', load the POST /api/v3/order schema, and execute it as a MARKET SELL of 0.5 BTC on BTCUSDT.

Key Endpoints

340 endpoints — the binance public spot api is the programmatic interface to binance's spot exchange, exposing 340 endpoints covering market data, spot trading, margin, sub-accounts, savings, futures-related lookups, fiat on-ramps, c2c, nft, and binance pay.

METHOD

PATH

DESCRIPTION

POST

/api/v3/order

Place a new spot order

DELETE

/api/v3/order

Cancel a spot order

GET

/api/v3/openOrders

List open orders

GET

/api/v3/account

Retrieve account information including balances

GET

/api/v3/klines

Fetch candlestick market data

GET

/api/v3/depth

Fetch order book depth

POST

/sapi/v1/margin/order

Place a margin order

POST

/sapi/v1/margin/borrow-repay

Borrow or repay on margin

POST

/api/v3/order

Place a new spot order

DELETE

/api/v3/order

Cancel a spot order

GET

/api/v3/openOrders

List open orders

GET

/api/v3/account

Retrieve account information including balances

GET

/api/v3/klines

Fetch candlestick market data

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Binance API keys and HMAC secrets are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens, and Jentic signs each request server-side — the raw X-MBX-APIKEY and signing secret never enter the agent's context.

Intent-based discovery

Agents search by intent (e.g., 'place a Binance spot order') and Jentic returns the matching Binance operation with its input schema and signature requirements, so the agent can call POST /api/v3/order without learning the HMAC signing scheme.

Time to first call

Direct Binance integration: 1-2 weeks for HMAC signing, websocket user-data streams, and reconnection handling. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Kraken

US- and EU-friendly crypto exchange API with comparable spot and margin scope

Choose Kraken for jurisdictions where Binance is restricted; choose Binance for the largest spot liquidity and product breadth.

Alternative

Bitfinex

Crypto exchange API with strong margin and derivatives support

Choose Bitfinex if your strategy targets its specific liquidity pools; choose Binance for the deepest spot order books.

Alternative

OKX

Crypto exchange API with unified trading and derivatives surface

Choose OKX when running a unified-account strategy across spot, margin, and derivatives; choose Binance for spot-first integrations.

Alternative

Bitstamp

Long-running EU-regulated crypto exchange API

Choose Bitstamp for EU-regulated trading with a smaller API surface; choose Binance for product breadth and depth.

FAQs

Specific to using Binance Public Spot API API through Jentic.

What authentication does the Binance Public Spot API use?

Trading and account endpoints require an API key in the X-MBX-APIKEY header, plus HMAC-SHA256 request signing using the matching secret. Public market-data endpoints like /api/v3/klines and /api/v3/depth do not require authentication. When called via Jentic, both the API key and the HMAC secret are held in the MAXsystem vault so the agent never sees the raw credentials.

Can I place spot and margin orders through the Binance API?

Yes. POST /api/v3/order places spot orders and supports MARKET, LIMIT, STOP_LOSS, and other order types, while POST /api/v3/orderList/oco places OCO order pairs. For margin trading, POST /sapi/v1/margin/order places cross or isolated margin orders, and POST /sapi/v1/margin/borrow-repay handles borrowing and repaying.

What are the rate limits for the Binance Spot API?

Binance applies weight-based rate limits at the IP level for market data and order limits at the account level. The exact weights are returned by GET /api/v3/exchangeInfo, and current order-count usage can be queried at GET /api/v3/rateLimit/order. The Jentic SDK retries on 429 responses with exponential back-off.

How do I place an order through Jentic?

Search Jentic for 'place a Binance spot order', which surfaces POST /api/v3/order. Load the schema, supply symbol, side, type, quantity, and price, and execute. The Python flow is: pip install jentic, then await client.search, await client.load, await client.execute.

Is the Binance Spot API free to use?

API access itself is free; trading fees are charged per executed order according to Binance's published fee schedule and the user's VIP tier. Use GET /api/v3/account/commission to retrieve current commission rates for the authenticated account.

Can I subscribe to real-time order and balance updates?

Yes. The /api/v3/userDataStream-style endpoints in the Stream group open and renew user-data streams that deliver real-time order, balance, and position updates over websocket. The REST API issues the listen key, and the websocket connection is then opened against the streaming endpoint.