/bonalog/organizations/financials

POST /api/bonalog/organizations/financials

Price: 5 credits

Get the official accounting (financial) statements of a Russian organization by its identifier

How to use it

Get the full official accounting (financial) statements of a Russian organization from the state register (ГИР БО) by its numeric identifier: one record per reporting year, each holding the statutory forms (balance sheet, statement of financial results, statement of changes in equity, cash-flow statement, statement of targeted funds use). Every form is returned as a list of line items keyed by their OKUD line code with current, previous and before-previous year values plus any explanation note. Use period to restrict to a single year. 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; >: 0)
• period string — Filter to a single reporting year; omit to return all available years (default: "")

Response

• @type string (default: "BonalogReport")
• id integer nullable
• period string nullable
• period_type string nullable (one of: "q1", "h1", "9m", "annual")
• presented_at string nullable
• publication integer nullable
• actual_bfo_date string nullable
• gain_sum number nullable
• actives number nullable
• knd string nullable
• has_audit boolean nullable
• is_cb boolean nullable
• correction_number integer nullable
• correction_date string nullable
• correction_version integer nullable
• required_audit boolean nullable
• okopf object nullable
  • @type string (default: "BonalogClassifier")
  • id string nullable
  • name string nullable
• okfs object nullable
  • @type string (default: "BonalogClassifier")
  • id string nullable
  • name string nullable
• forms array
  • @type string (default: "BonalogReportForm")
  • form string required
  • okud string nullable
  • lines array
    • @type string (default: "BonalogReportLine")
    • line string required
    • current number nullable
    • previous number nullable
    • before_previous number nullable
    • explanation 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 — 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.