/sravni/microfinance-companies/search

POST /api/sravni/microfinance-companies/search

Price: 5 credits

Search the Sravni.ru microfinance company (MFO) directory

How to use it

Search the directory of Russian microfinance companies (MFO) on Sravni.ru, optionally filtered by name keyword. Returns each company's name, full legal name, description, license, website, address, phones, Sravni rating, review count, logo, and offered loan services.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string nullable — Filter microfinance companies by name (examples: "Займер")
• count integer required — Number of microfinance companies to return (min: 1)

Response

• @type string (default: "SravniOrganization")
• id string required
• alias string nullable
• name string nullable
• full_name string nullable
• type string nullable
• status string nullable
• description string nullable
• license string nullable
• image string nullable
• square_image string nullable
• website string nullable
• address string nullable
• legal_address string nullable
• phones array (default: [])
• emails array (default: [])
• ogrn string nullable
• inn string nullable
• kpp string nullable
• bik string nullable
• swift string nullable
• cb_website string nullable
• registration_date string nullable
• rating_value number nullable
• review_count integer nullable
• branch_count integer nullable
• ra_rating string nullable
• is_partner boolean (default: false)
• services array (default: [])
  • @type string (default: "SravniOrganizationService")
  • key string required
  • label string nullable
  • alias string nullable
  • product_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 — 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.