/moex/securities/history

POST /api/moex/securities/history

Price: 5 credits

Get end-of-day OHLC price history for a Moscow Exchange security

How to use it

Get end-of-day (daily) OHLC price history for a Moscow Exchange (MOEX) security by ticker (SECID). Returns per-day bars with open/high/low/close, legal close and weighted-average prices, volume and value traded, number of trades, market price and currency. Use date_from/date_to (YYYY-MM-DD) to set the range, engine/market for the segment (default stock/shares) and board to restrict to one board.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• security string required — Security ticker (SECID) (examples: "SBER", "GAZP"; minLength: 1)
• count integer required — Number of daily bars to return (min: 1)
• engine string — Trading engine (default: "stock"; one of: "stock", "currency", "futures", "commodity", "agro", "otc", "money", "quotes", "state")
• market string — Market within the engine (default: "shares"; one of: "shares", "bonds", "index", "foreignshares", "ndm", "repo", "ccp", "otc", "standard", "classica", "selt", "forts", "options", "indicativerates")
• board string nullable — Board ID to restrict history to a single board (e.g. TQBR)
• date_from string nullable — Start date (YYYY-MM-DD) (examples: "2024-01-01")
• date_to string nullable — End date (YYYY-MM-DD) (examples: "2024-12-31")

Response

• @type string (default: "MoexHistoryBar")
• secid string required
• board_id string nullable
• trade_date string nullable
• open number nullable
• high number nullable
• low number nullable
• close number nullable
• legal_close_price number nullable
• wa_price number nullable
• volume integer nullable
• value number nullable
• num_trades integer nullable
• market_price number nullable
• currency string 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 — Security not found or no history available for the requested range 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.