/cbr/rates/history

POST /api/cbr/rates/history

Price: 1 credit

Get the historical exchange rate of a single currency against the ruble over a date range

How to use it

Get the historical official Bank of Russia exchange rate of one foreign currency against the ruble over a date range. Pass the currency as its ISO character code (USD, EUR, CNY) or its Bank-of-Russia id (R01235). Returns one record per published day with the nominal, the rate for that nominal, and the per-unit rate.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• currency string required — Currency to read the history for — either the Bank-of-Russia id (e.g. R01235) or the ISO character code (e.g. USD) (examples: "USD", "R01235", "EUR", "CNY"; minLength: 1)
• date_from string required — Start date in YYYY-MM-DD format (pattern: ^\d{4}-\d{2}-\d{2}$)
• date_to string required — End date in YYYY-MM-DD format (pattern: ^\d{4}-\d{2}-\d{2}$)
• count integer required — Maximum number of records to return (min: 1)

Response

• @type string (default: "CbrRateBar")
• date string required
• nominal integer nullable
• value number nullable
• unit_rate number 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 — No rate history found for the given currency and date 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.