/bonalog/organizations/search

POST /api/bonalog/organizations/search

Price: 1 credit

Search Russian organizations by name, INN, OGRN, address or activity code

How to use it

Search the Russian state register of accounting statements (ГИР БО) for organizations by name, taxpayer number (INN), registration number (OGRN), address substring or OKVED2 activity code. Filters can be combined and narrowed by reporting year, reporting-period type and credit-organization status. Returns matching organizations with their numeric identifier (for the get-by-id and financials endpoints), basic registry fields and a summary of their latest accounting statement.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string — Organization name or INN to search for (default: ""; examples: "Газпром")
• inn string — Filter by exact taxpayer number (INN) (default: ""; examples: "7736050003")
• ogrn string — Filter by exact primary state registration number (OGRN) (default: "")
• address string — Filter by address substring (region, city, street) (default: "")
• okved2 string — Filter by OKVED2 activity code or its prefix (default: ""; examples: "46.71")
• period string — Filter by accounting-statement reporting year (default: ""; examples: "2024")
• period_type string nullable — Filter by reporting-period type: 3=Q1, 6=H1, 9=9 months, 12=annual (one of: "3", "6", "9", "12")
• is_cb boolean nullable — Filter to credit organizations only
• all_fields_match boolean — Require all provided filters to match exactly (default: false)
• count integer required — Max number of results (min: 1)

Response

• @type string (default: "BonalogOrganizationSearchItem")
• id integer required
• inn string nullable
• ogrn string nullable
• short_name string nullable
• status_code string nullable
• status_date string nullable
• address object nullable
  • @type string (default: "BonalogAddress")
  • index string nullable
  • region string nullable
  • district string nullable
  • city string nullable
  • settlement string nullable
  • street string nullable
  • house string nullable
  • building string nullable
  • office string nullable
• okved2 string nullable
• okopf integer nullable
• report object nullable
  • @type string (default: "BonalogOrganizationSearchBfo")
  • period string nullable
  • actual_bfo_date string nullable
  • gain_sum number nullable
  • knd string nullable
  • has_audit boolean nullable
  • actual_correction_number integer nullable
  • actual_correction_date string nullable
  • is_cb boolean 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.