Quick start

This guide gets you from zero to three working API calls in under five minutes. Step 1 needs no signup and no API key — copy the cURL, paste it, done. Steps 2 and 3 stay on the zero-auth Category A surface so you can evaluate the contract before registering.

Step 1 — Your first call (no auth required)

These public endpoints need no API key. Copy the cURL below and run it in your terminal:

curl "https://apier.no/api/v1/public/obligations?entity_type=AS"

You'll get back a JSON payload listing every regulatory obligation that applies to a Norwegian AS (aksjeselskap) — MVA registration, skattemelding, årsregnskap, A-melding, and the revisor thresholds — each one with its legal citation and a tier_2_required flag marking the ones that need a delegated system user before a concrete company-specific verdict can be computed:

{
  "success": true,
  "data": [
    {
      "obligation_id": "MVA_REGISTRATION_THRESHOLD",
      "obligation_name": "mva_registration",
      "required": "conditionally",
      "tier_2_required": true,
      "legal_basis": "Merverdiavgiftsloven § 2-1",
      "applies_to_entity_types": ["AS"]
    },
    {
      "obligation_id": "SKATTEMELDING_AS",
      "obligation_name": "skattemelding",
      "required": "always",
      "tier_2_required": false,
      "legal_basis": "Skatteforvaltningsloven § 8-2",
      "applies_to_entity_types": ["AS"]
    }
  ],
  "_meta": {
    "rulebook_version": "1.0.0",
    "data_freshness": "2026-04-22T10:05:07.813Z",
    "last_verified": "2026-04-21T10:05:07.813Z",
    "source": "apier.no",
    "data_source": "Brønnøysund Enhetsregisteret + Apier Universal Rulebook",
    "legal_basis": "NLOD — public registry reuse",
    "schema_version": "1.0.0"
  }
}

That's one call, no auth, real regulatory data.

Step 2 — Decode the _meta envelope

Every Rulebook-influenced response carries a _meta block. It's the trust signal agents build reasoning on:

• rulebook_version — which Rulebook the verdict was computed under. A bump means the rules may have changed.
• data_freshness — when this data was last fetched from the upstream registry (ISO 8601 UTC).
• last_verified — the most recent manual verification timestamp. Framed per CLAUDE.md Rule 8 as "Verified against [source] version [X] as of [date]."
• data_source — authoritative origin, e.g. Brønnøysund Enhetsregisteret. Distinct from source (the response origin: apier.no).

Agents can diff rulebook_version across two calls to detect whether a rule change happened between them — and can surface last_verified to end users as an auditable reference.

Step 3 — A second zero-auth endpoint

Try the calendar-year deadlines endpoint. Same zero-auth contract, same _meta envelope, weekend-and-holiday-adjusted Europe/Oslo dates. Omitting year defaults to the current Oslo calendar year:

curl "https://apier.no/api/v1/public/deadlines?year=2026"

The response lists every Norwegian obligation deadline for the requested calendar year (MVA terminer, A-melding, skattemelding, årsregnskap — January 1 through December 31 of year). Each entry carries an applies_to_entity_types array so an agent filtering for AS or ENK can pick the relevant rows in one pass.

Or pull a Norges Bank exchange rate — the third zero-auth endpoint:

curl "https://apier.no/api/v1/tools/exchange-rate?currency=EUR"

All three of these endpoints are Category A: no API key, no rate limit per consumer (soft IP-based cap only), and documented at /openapi.json with OpenAPI 3.1 examples fields you can copy verbatim.

What's next

To go beyond the public surface — per-company obligations, filing status, action submission — you'll need an API key. Category B endpoints (/api/v1/company/{org}/*) require Authorization: Bearer <YOUR_API_KEY> and are per-key-rate-limited by tier.

• Authentication — the full auth model, key issuance, and tier limits.
• Endpoint reference — every operation, backed by /openapi.json.
• Recipes — golden-path agent workflows with full request/response examples.

If an endpoint returns an error, every 4xx/5xx carries a structured error_code + explanation — the full shape is covered in Error handling.