/banki/ratings/search

POST /api/banki/ratings/search

Price: 10 credits

Rank Russian banks by a financial indicator (CBR data) on Banki.ru

How to use it

Rank Russian banks by a financial indicator on Banki.ru (sourced from Central Bank of Russia reporting). Returns a leaderboard of banks ordered by the chosen metric (net assets, net profit, capital, loan portfolio, retail/corporate loans and deposits, securities, return on assets/equity, etc), each with its rank, current value, and previous-period value. Optionally pick a reporting period.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• count integer required — Number of banks to return (min: 1)
• metric string — Financial indicator to rank banks by (default: "net_assets"; one of: "net_assets", "net_profit", "capital", "loan_portfolio", "overdue_debt", "retail_loans", "corporate_loans", "retail_deposits", "corporate_funds", "securities", "highly_liquid_assets")
• period string nullable — Reporting period as the first day of a month (YYYY-MM-01); defaults to the latest period (examples: "2026-05-01", "2026-01-01")

Response

• @type string (default: "BankiRatingEntry")
• place integer required
• bank_id integer required
• name string required
• licence string nullable
• region string nullable
• value integer nullable
• previous_value 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 — The entity was not found, or a precondition failed 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.