Category
Data, or execution?
A company-data API gives you registry facts — that a company exists, who holds roles, NACE codes, status. That is a different job from acting on those facts correctly, legally and predictably.
What a company-data API gives you
Lookups: that a company exists, its entity type, NACE codes, status, roles and signing authority. Valuable facts — but still just facts. They tell you what is true, not what you are allowed to do with it.
What execution actually requires
- Who can act. Signing authority, prokura and delegated System User scopes must be resolved before a binding action is attempted.
- Validation before submitting. Does the company exist, is the System User authorised, are the scopes delegated, is the payload valid — checked before anything is sent.
- Deadlines and obligations. What is due, when, and in Oslo time — derived, not guessed.
- Receipts and audit trail. A signed receipt for every action and an immutable trail — so you can show what was done, and why.
Apier is the execution layer
Apier does not replace the registries — it builds on them. As a category, the difference is simple: a data API answers “what is true?”, while the execution layer answers “what am I allowed to do, and how do I do it safely?”. If you would rather build that layer yourself, we have laid out the maths.
Related pages
- Direct integration vs Apier — build the stack yourself vs use Apier.
- Brønnøysund (BRREG) API — the company-data source itself.
- Pricing and the documentation.
Get started
Try the company-data endpoints in the sandbox with no signup, or read the documentation.