/bonalog/organizations

POST /api/bonalog/organizations

Price: 1 credit

Get a Russian organization's registry card by its identifier

How to use it

Get the full registry card of a Russian organization from the state register of accounting statements (ГИР БО) by its numeric identifier. Returns INN, OGRN, KPP, full and short names, status, registration date, authorized capital, legal address, classifier codes with their names (OKVED2 activity, OKOPF legal form, OKFS ownership form), the supervising tax authority, and the list of available accounting-statement periods with revenue and assets summaries. The numeric id is obtained from the search endpoint.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• id integer required — Organization identifier (examples: 6622458, 8211141; >: 0)

Response

• @type string (default: "BonalogOrganization")
• id integer required
• inn string nullable
• ogrn string nullable
• kpp string nullable
• full_name string nullable
• short_name string nullable
• status_code string nullable
• status_date string nullable
• registration_date string nullable
• authorized_capital number nullable
• is_active boolean 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 object nullable
  • @type string (default: "BonalogClassifier")
  • id string nullable
  • name string nullable
• okopf object nullable
  • @type string (default: "BonalogClassifier")
  • id string nullable
  • name string nullable
• tax_authority object nullable
  • @type string (default: "BonalogTaxAuthority")
  • id integer nullable
  • name string nullable
  • code integer nullable
  • latitude number nullable
  • longitude number nullable
  • type string nullable
  • parent_id integer nullable
• reports array
  • @type string (default: "BonalogReportSummary")
  • period string nullable
  • publication integer nullable
  • actual_bfo_date string nullable
  • gain_sum number nullable
  • actives number nullable
  • knd string nullable
  • has_audit boolean nullable
  • actual_correction_number integer nullable
  • actual_correction_date string nullable
  • published_correction_number integer nullable
  • published_correction_date string nullable
  • is_cb boolean nullable
  • msp_category string nullable
  • published 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 — Organization 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.