/banki/banks

POST /api/banki/banks

Price: 20 credits

Get a Banki.ru bank profile by alias or numeric bank id

How to use it

Get the full profile of a Russian bank on Banki.ru by its alias (e.g. 'alfabank') or numeric bank id (e.g. '325'). Returns the bank's name, logo, official website, region and address, CBR licence number, OGRN, BIK, registration date, ownership flags (state/foreign/non-bank-credit-organization), deposit insurance membership, financial rating place, people's-rating (Narodny Reyting) place, question/answer counts, call-center phones, social and app-store links, and agency credit ratings.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• bank string required — Bank alias ('alfabank') or numeric bank id ('325') or bank page URL (examples: "alfabank", "325", "sberbank"; minLength: 1)

Response

• @type string (default: "BankiBank")
• id integer required
• alias string required
• name string required
• name_full string nullable
• name_eng string nullable
• name_full_eng string nullable
• name_alternative string nullable
• image string nullable
• mobile_logo string nullable
• head_office_image string nullable
• website_url string nullable
• region string nullable
• address string nullable
• address_eng string nullable
• licence string nullable
• ogrn string nullable
• bik string nullable
• type string nullable
• registration_date string nullable
• description string nullable
• description_eng string nullable
• personal_director string nullable
• cbr_url string nullable
• is_state_bank boolean (default: false)
• is_foreign_bank boolean (default: false)
• is_nco boolean (default: false)
• is_top_bank boolean (default: false)
• is_deposit_insurance_member boolean (default: false)
• is_active boolean (default: false)
• available_in_mobile_app boolean (default: false)
• financial_rating_place integer nullable
• people_rating_place integer nullable
• people_rating_total integer nullable
• question_count integer nullable
• answer_count integer nullable
• avg_response_time integer nullable
• phones array (default: [])
  • @type string (default: "BankiBankPhone")
  • phone string required
  • description string nullable
• social_links object nullable
  • @type string (default: "BankiBankSocialLinks")
  • vk string nullable
  • telegram string nullable
  • ok string nullable
  • appstore string nullable
  • rustore string nullable
  • appgallery string nullable
  • googleplay string nullable
• credit_ratings array (default: [])
  • @type string (default: "BankiBankCreditRating")
  • agency string required
  • rating string nullable
  • forecast string nullable
  • active_from string nullable
• url 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 — Bank not 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.