/brreg/companies/accounts

POST /api/brreg/companies/accounts

Price: 1 credit

Get the submitted annual financial statements of a Norwegian legal entity by its organization number from the Register of Company Accounts (Regnskapsregisteret). Each statement includes the accounting period, currency, accounting rules, balance sheet totals (assets, equity, liabilities) and the income statement (operating income/costs/result, net financial items, result before tax, annual result).

How to use it

Get the annual financial statements (balance sheet and income statement totals) of a Norwegian company by its organization number (e.g. '923609016'). Returns one item per submitted accounting period. May return an empty list if no accounts have been submitted.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• organization_number string required — Norwegian organization number (9 digits) (examples: "923609016")

Response

• @type string (default: "BrregAccount")
• id string nullable
• journal_number string nullable
• accounts_type string nullable
• organization_form string nullable
• is_parent_company boolean nullable
• period_from string nullable
• period_to string nullable
• currency string nullable
• accounting_rules string nullable
• is_small_company boolean nullable
• is_liquidation_accounts boolean nullable
• is_audited boolean nullable
• total_assets number nullable
• total_current_assets number nullable
• total_fixed_assets number nullable
• total_equity_and_liabilities number nullable
• total_equity number nullable
• total_liabilities number nullable
• total_short_term_liabilities number nullable
• total_long_term_liabilities number nullable
• operating_income number nullable
• operating_costs number nullable
• operating_result number nullable
• net_financial_items number nullable
• result_before_tax number nullable
• annual_result number 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 — No legal entity found for the given organization number 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.