/binance/tickers

POST /api/binance/tickers

Price: 1 credit

Get price-change statistics for one or more trading pairs over a rolling window

How to use it

Get rolling price-change statistics for one or more Binance spot trading pairs (e.g. 'BTCUSDT'). For each pair it returns the last price, price change and percent change, weighted average price, open/high/low prices, base and quote volume, the number of trades, and the window's open and close times. With the default 24-hour window it also includes the current best bid/ask prices and sizes, previous close, and last trade size. Set window_size (e.g. '1h', '4h', '1d') for a rolling window other than 24 hours.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• symbols array required — Trading pair symbols, uppercase, no separator (examples: ["BTCUSDT","ETHUSDT"]; minItems: 1)
• window_size string nullable — Rolling window for the statistics, e.g. '1h', '4h', '1d'. When omitted, a fixed 24-hour window is used (examples: "1d", "4h")

Response

• @type string (default: "BinanceTicker")
• symbol string required
• price_change number nullable
• price_change_percent number nullable
• weighted_avg_price number nullable
• prev_close_price number nullable
• last_price number nullable
• last_qty number nullable
• bid_price number nullable
• bid_qty number nullable
• ask_price number nullable
• ask_qty number nullable
• open_price number nullable
• high_price number nullable
• low_price number nullable
• volume number nullable
• quote_volume number nullable
• open_at integer nullable
• close_at integer nullable
• first_id integer nullable
• last_id integer nullable
• trade_count integer nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — None of the requested trading pairs were found Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.