# Change monitoring for Norwegian companies

Canonical: https://www.apier.no/monitoring

Apier watches Brønnøysund's registers and keeps every change it observes in an append-only archive. An AI agent can be told when a company it works with changes, by a signed webhook, or it can read the same changes from the archive.

An alert says what changed in the register and when. An agent uses it to flag the change for a person to look at; it is not a reading of who may act for the company.

## What is detected

Change alerts have five event types. Each event carries the value before and after the change, the effective date where Brønnøysund gives one, the date Apier observed the change, the source and the id of the archived change it comes from.

| Event type | When it fires |
|---|---|
| `signing_rule_changed` | The registered signature (signaturrett) or prokura rules change. |
| `role_added` | A role holder is added to the board, or as the owner of a sole proprietorship. |
| `role_removed` | A role holder is removed. |
| `status_changed` | The company's status changes, for example to bankrupt, in liquidation, forcibly dissolved or deleted. |
| `vat_registration_changed` | The company is registered in, or removed from, the VAT register (Merverdiavgiftsregisteret). |

Events never name a person: a role event says which role was added or removed, and a signing event lists the role labels and signing rules, not who holds them. To see who holds a role now, call `GET /api/v1/company/{org}/authority`.

## How often Apier looks

Apier polls; Brønnøysund does not push. These are the scheduled jobs between a change in the register and the alert reaching you, with the schedule each runs on.

| Job | Runs | What it does |
|---|---|---|
| `brreg-updates-feed` | at 20 minutes past every hour | Reads Brønnøysund's update feed for the Central Coordinating Register and archives what changed. |
| `brreg-roller-feed` | at 40 minutes past every hour | Reads Brønnøysund's role feed and the registered signature and prokura for the companies it refreshes. |
| `bulk-file-vault` | once a day | Stores the national register file, the source of Apier's daily archive. |
| `change-alerts` | at 50 minutes past every hour | Turns the archived changes for watched companies into alert events. |
| `webhook-delivery` | every minute | Sends pending alerts to your webhook and retries a failed delivery with backoff. |

A change one of the hourly feeds archives is turned into an alert by the next alert run, and the delivery job then sends it. Alerts cover companies Apier mirrors from the Brønnøysund update feeds.

## Where the archive starts

Apier's Brønnøysund archive starts on 2026-07-30. Changes before that day are not in it, and Apier claims none. Every historical answer states the window it covers.

The archive is append-only: an observed change is never rewritten or removed. The one exception is a record Brønnøysund itself removes, which is kept as a tombstone with the date and the reason.

## How an agent subscribes

### Push: a watchlist with signed webhooks

An account watches up to 100 companies. The watchlist is managed from a dashboard session: the first company you add creates it, with your webhook URL and the account key whose wallet and spend caps pay for it. The signing secret is shown once, in that first response.

Each delivery is a `POST` to your URL with the header `x-apier-signature: t=<unix seconds>,v1=<hex>`, an HMAC over the timestamp, a dot and the raw body. Answer with any `2xx`; other answers are retried with backoff. You can watch a subset of the five event types.

### Pull: read the change archive

An agent that polls instead reads the archive with `GET /api/v1/changes` or the MCP tool `list_changes`, with an API key that carries the `read:changes` scope. Filter by `entity_id` (the org number), `source`, `change_type` and a `from` to `to` range; pages are newest first and carry a signed cursor. Queries without `entity_id` leave out rows with personal fields. Every row carries `observation_kind`: `first_observation` marks the first time the archive saw a value, not a change in the company, and `value_change` marks an observed change. Count only `value_change` rows as changes.

```bash
curl -H 'Authorization: Bearer <API_KEY>' \
  'https://www.apier.no/api/v1/changes?entity_id=999999999&from=2026-11-01T00:00:00Z'
```

### Test without a watchlist

`GET /api/v1/sandbox/watchlist/events` returns one synthetic alert of each event type, shaped like the `change` object of a real delivery. It accepts the sandbox bearer and costs nothing; the sandbox returns events by polling and never sends a webhook.

## What it costs

Change alerts follow the Annual Accounts Monitor's wallet rules: each watched company is charged the Monitor's monthly price once per calendar month (Europe/Oslo), and once only when you also monitor its accounts. Deliveries cost nothing extra. Wallet billing for the Monitor is coming; existing Professional and Enterprise subscriptions have change alerts to the end of their period. The pricing page has the current terms.

## What monitoring is not

An alert is a record of what Apier observed in a public register. It is not a verdict on whether anyone may sign or act for the company, it does not stop or approve anything by itself, and it is not legal advice. The authority endpoint returns the register's coded signing rules for the company as they stand.

## Read more

- [Change alerts guide](https://www.apier.no/docs/guides/change-alerts)
- [Pricing](https://www.apier.no/pricing)
- [Capability status](https://www.apier.no/docs/capability-status)
