How to get every check on a Norwegian company in one call
Call GET /api/v1/company/{org}/checks to get registration status, bankruptcy and liquidation flags, VAT, roles, coded signing authority, annual accounts, requirements evidence and the LEI status, each with its own status, source and freshness, and no verdict.
[Cite this as: Apier.no Docs v0.1.0 — last updated 2026-11-01]
The check bundle returns every relevant check on one Norwegian company in a single call. Each check is listed in a fixed order and carries its own status, the fact as Apier read it, the source, the source URL, when it was read, how fresh it is and the licence it was obtained under.
The bundle is a list of facts. It never gives a verdict: there is no summary field, no overall status and no count of checks. You decide what the facts mean for your use.
| Check | What it reads |
|---|---|
registration_status | The company's status in Enhetsregisteret. |
bankruptcy_liquidation | The bankruptcy, liquidation and forced liquidation flags. |
vat_registration | Whether the company is registered in the VAT register. |
roles | How many signaturrett and prokura holders are registered (no names). |
coded_signing_authority | The coded state of the signature and prokura rules. |
annual_accounts_filed | Whether annual accounts are on file, and the latest year. |
requirements_evidence | Which facts to check for the requirements that apply to the company's type today. |
lei_status | The company's LEI as GLEIF records it: the LEI, its registration status, entity status and next renewal date. Read from Apier's own daily archive of GLEIF's LEI records (CC0 1.0). A LAPSED LEI is stale; no LEI mapped to the org number is missing. |
Step 1 — Call the endpoint
curl -H "Authorization: Bearer $APIER_API_KEY" \
https://www.apier.no/api/v1/company/{org}/checksReplace {org} with the company's 9-digit organisasjonsnummer. The fixture
999999999 exists only in the sandbox (Step 5), so production does not
resolve it.
The key needs the read:brreg scope. The call is billed as one company
read.
Step 2 — Read the status of each check
Every entry has a check_status with one of five values:
| Status | Meaning |
|---|---|
verified | The source answered and the fact is on record. An adverse fact, such as a bankruptcy flag, is still a verified fact. |
missing | The source answered and the fact is not on record. |
stale | The fact is on record but older than the source's freshness window. |
unavailable | The source could not be read on this call. This is never a failed check. |
not_checked | Nothing was evaluated for this check. |
Read the value of each entry for the fact itself, and freshness for how
recent it is: served_from, max_age_days and stale.
Step 3 — Handle a source that is down
When a source cannot be read, its own checks answer unavailable and the
call still returns 200 with every other check filled in. Retry later for the
unavailable checks; do not read them as a negative answer.
When every check is unavailable or not_checked, nothing was evaluated
and the call is not charged: _meta.cost_nok is 0. The LEI status comes from
Apier's own archive, so it never makes a call billable on its own: when every
other check is unavailable or not_checked, the call is not charged either.
Step 4 — Ask for a signed copy
Add ?certificate=true to get the bundle wrapped in a signed certificate
that you can verify offline against /.well-known/jwks.json, the same way
as described in How to verify an apier certificate.
curl -H "Authorization: Bearer $APIER_API_KEY" \
"https://www.apier.no/api/v1/company/{org}/checks?certificate=true"Any unknown query parameter is refused with 400 VALIDATION_FAILED.
Step 5 — Replay a past date
Add ?as_of=YYYY-MM-DD to re-run the bundle as of the end of that
Europe/Oslo day:
curl -H "Authorization: Bearer $APIER_API_KEY" \
"https://www.apier.no/api/v1/company/999999999/checks?as_of=2026-10-15"A replay reads only what Apier had archived by the end of that day and the requirements version in force on that date. It never fills a gap with today's value:
- A fact Apier had not observed by then is
not_checked; a source that could not be read isunavailable. - The bankruptcy and liquidation flags, the coded signing authority and
the annual accounts filing status are not archived, so they are
not_checkedon every replay. - Apier's archive starts on 2026-07-30. Every earlier date is
not_checkedthroughout, and_meta.coveragestates the window.
The answer carries replayed: true and replay_date. Two replays of the
same date on the same archive state return the same body. A replay is
charged like a live call, and is not charged when nothing was evaluated. A
future, malformed or repeated date is refused with 400 VALIDATION_FAILED.
The evidence pack takes the same as_of: a past date packs the replayed
bundle.
Step 6 — Try it in the sandbox
GET /api/v1/sandbox/company/{org}/checks returns the same bundle over
synthetic fixtures with a sandbox bearer, and is never charged. In the
sandbox the coded signing authority, the requirements evidence and the LEI
status answer not_checked, because those checks read stores the sandbox
does not use. ?as_of= replays a fixed historical fixture: the sandbox
archive observed every fixture on 2026-08-01, so a replay on or after that
day serves the fixture's fields and an earlier one has nothing observed.
From an MCP client, call get_company_verification with mode: "checks".
How to record an action hash with a notary record
Record the SHA-256 hash of an action your agent took, citing your own Apier receipts, and get a receipt that verifies offline. A record proves only that API key K recorded hash H, citing Apier receipts R, at time T.
How to verify an evidence pack
Call GET /api/v1/company/{org}/evidence-pack to get one signed record of what Apier observed about a Norwegian company, then check its signature against the public key set and each archived record's anchor proof against the published daily roots.