Hopp til innhold

Apier.no

Oppskrifter

Menneskelesbare gjennomganger av de kanoniske arbeidsflytene for agenter. Hver oppskrift speiler nøyaktig én oppføring i /workflows.json, det maskinlesbare manifestet som crawlere og agentrammeverk bruker. For hele evnelisten, se /api/v1/capabilities.

Jobbformede oppskrifter

Gjennomganger med oppgaven først for de fire kombinasjonene i drift: jobboppskrifter og oppskrifter «for plattformer» per kombinasjon, pluss en sammensatt KYB-kjede for kundeoppstart.

Look up Norwegian business deadlines for a year

workflow.lookup-deadlines · Slå opp norske forretningsfrister for et år

Hent den kanoniske fristlisten (MVA-terminer, A-melding, skattemelding, årsregnskap, årsbekreftelse til Foretaksregisteret) for et kalenderår. Fristene er allerede flyttet forbi helger og norske helligdager, og den opprinnelige lovfristen vises i `adjusted_from` når det er relevant.

Intensjon
Find all upcoming Norwegian business deadlines for a given calendar year.
Forventet resultat
An ordered list of deadline entries sorted ascending by date, each with obligation_id, legal deadline, adjusted deadline (when pushed for weekends/holidays), and legal reference.
Utløsende intensjon
“What Norwegian business deadlines are coming up in YYYY?”
Estimert tid
~200 ms · ingen autentisering

Steg

  1. 1

    Call GET /api/v1/public/deadlines?year=YYYY and iterate the returned mappings sorted ascending by deadline.

    public.deadlines → JSON envelope with data.year, data.deadlines[] (sorted ascending), and _meta.served_from='static'.

Agentinstruksjoner

1. Call GET /api/v1/public/deadlines?year=<YYYY> (no authentication required).
2. Parse the response body at data.deadlines — it is sorted ascending by deadline.
3. For each entry, note obligation_id, deadline (ISO 8601 with Europe/Oslo offset), and adjusted_from (null unless the legal deadline fell on a weekend or holiday).
4. If data.deadlines is empty, the year is valid but outside our coverage window (2020-2100) — surface VALIDATION_FAILED explanation to the user.

Feilmoduser å planlegge for

  • invalid_year
  • upstream_timeout

Eksempelforespørsel

GET /api/v1/public/deadlines?year=2026

Check a Norwegian company's current Brønnøysund status

workflow.check-company-status · Sjekk en norsk virksomhets gjeldende Brønnøysund-status

Hent dagens nivå 1-visning av et norsk selskap ut fra organisasjonsnummeret. `data.data_tier` oppgir hvilket nivå som ble levert (nivå 2 leveres ikke i dag: delegeringsporten ble trukket tilbake 2026-10-21); `_meta.served_from` skiller hurtigbuffer fra direkte oppslag.

Intensjon
Retrieve the current Brønnøysund-sourced status and registry metadata for a Norwegian company.
Forventet resultat
Company context object with name, entity_type, NACE codes, status (active/deregistered/dissolved), municipality, signaturrett/prokura; the Tier 2 block self-describes as unavailable.
Utløsende intensjon
“Is company with org_number 999999999 still active, and what is its current name?”
Estimert tid
~500 ms · krever API-nøkkel

Steg

  1. 1

    Call GET /api/v1/company/{org}/context with the consumer API key; branch on data.data_tier.

    company.context → JSON envelope with data.company (tier-1 fields), optional data.tier_2 block, data.data_tier, and _meta with served_from + stale markers.

Agentinstruksjoner

1. Ensure you hold a consumer API key in the Authorization: Bearer header.
2. Call GET /api/v1/company/<ORG_NUMBER>/context with ORG_NUMBER as a 9-digit Norwegian organisation number.
3. Read data.data_tier — 'tier_1' means public Brønnøysund fields; 'tier_2' is not served today (its delegation gate was withdrawn on 2026-10-21).
4. Read _meta.served_from ('cache' vs 'live') and _meta.stale (true when a within-limit cached row was served as an upstream-down fallback).
5. On 404 org_not_found: surface the explanation.why text (Norwegian) to the user.
6. On 503 with _meta.stale=true: the data is still usable but older than 24 hours — tell the user freshness is degraded.

Feilmoduser å planlegge for

  • org_not_found
  • tier2_data_missing
  • upstream_timeout
  • auth_missing
  • auth_invalid_key

Eksempelforespørsel

curl -H 'Authorization: Bearer <API_KEY>' https://www.apier.no/api/v1/company/999999999/context

Look up the official NOK exchange rate for a date

workflow.exchange-rate-lookup · Slå opp offisiell NOK-kurs for en dato

Hent Norges Banks NOK-kurs for en valuta og en dato. For en helg, en helligdag eller dagens dato før dagens kurs er publisert, brukes siste foregående virkedag; `data.date` er den faktiske publiseringsdatoen, og `data.requested_date` er datoen det ble spurt om.

Intensjon
Fetch the official Norges Bank NOK exchange rate for a currency and optional date, with automatic fallback to the most recent prior business day when the requested date is a weekend, holiday, or before today's ~16:00 Oslo publication.
Forventet resultat
A rate object: base='NOK', quote=<uppercased ISO>, rate (1 quote = rate NOK), date (actual publication date), requested_date (what you asked for), source='Norges Bank'.
Utløsende intensjon
“What was the EUR/NOK rate on 2026-04-10?”
Estimert tid
~300 ms · ingen autentisering

Steg

  1. 1

    Call GET /api/v1/tools/exchange-rate?currency=<ISO>&date=<YYYY-MM-DD>.

    tools.exchange_rate → JSON envelope with data.rate (number), data.date, data.requested_date, data.cached, and _meta.served_from (cache/live).

Agentinstruksjoner

1. Call GET /api/v1/tools/exchange-rate?currency=<ISO>&date=<YYYY-MM-DD> (no authentication).
2. CURRENCY must be a 3-letter ISO 4217 code Norges Bank tracks (EUR, USD, GBP, SEK, DKK, etc.).
3. DATE is optional — omit to get today-in-Oslo; future dates are rejected with 400 INVALID_DATE.
4. Compare data.date to data.requested_date. If they differ, the requested date fell on a weekend / holiday / pre-publication window and the rate is from the most recent prior business day.
5. On 404 NO_RATE_AVAILABLE: Norges Bank does not track this currency — try EUR or USD as a fallback.
6. On 502 UPSTREAM_UNAVAILABLE: transient; retry in a few minutes.

Feilmoduser å planlegge for

  • invalid_currency
  • invalid_date
  • no_rate_available
  • upstream_unavailable

Eksempelforespørsel

GET /api/v1/tools/exchange-rate?currency=EUR&date=2026-04-10

Translate an Altinn 2 code to the Altinn 3 equivalent

workflow.altinn-role-migration · Oversett en Altinn 2-kode til Altinn 3-motparten

Oversett en tjeneste eller rollekode fra Altinn 2 til motparten i Altinn 3. Fristen for utfasing av Altinn 2, 19. juni 2026, er passert, så dette viser hva en eldre kode tilsvarer når en migrering skal ryddes opp. La migreringshandlinger i produksjon kreve `verified === true`; ubekreftede oppføringer er bare oppslag for enkelhets skyld.

Intensjon
Discover the Altinn 3 resource or role that replaces a given Altinn 2 service/role code, now that the 19 June 2026 Altinn 2 deprecation cliff has passed.
Forventet resultat
A migration entry with altinn2_code, altinn3_code (possibly null if DigDir hasn't published an equivalent yet), migration_notes in Norwegian and English, service_owner, and a `verified` flag indicating whether the mapping has been cross-checked against DigDir's authoritative source.
Utløsende intensjon
“What Altinn 3 role corresponds to Altinn 2 code A0208?”
Estimert tid
~150 ms · ingen autentisering

Steg

  1. 1

    Call GET /api/v1/tools/altinn-migration?altinn2_code=<CODE>; inspect `verified` before trusting the mapping for production automation.

    tools.altinn_migration → JSON envelope with data.entry (MigrationEntry), data.deprecation_deadline, data.days_remaining, data.deadline_passed, and _meta.served_from='static'.

Agentinstruksjoner

1. Call GET /api/v1/tools/altinn-migration?altinn2_code=<CODE> (no authentication). CODE is alphanumeric, max 10 characters (e.g. A0208).
2. Read data.entry.verified — if false, the mapping is a best-effort reference and MUST NOT drive production migration without human review.
3. Read data.entry.altinn3_code — null means DigDir has not yet published the Altinn 3 equivalent.
4. The 19 June 2026 Altinn 2 cliff has passed, so data.deadline_passed is true and data.days_remaining is 0 — tell the user the cutoff is already behind them rather than presenting a countdown.
5. On 404 NOT_FOUND: the code is not in our static map — point the user at docs.altinn.studio.

Feilmoduser å planlegge for

  • invalid_code
  • not_found
  • unverified_entry

Eksempelforespørsel

GET /api/v1/tools/altinn-migration?altinn2_code=A0208

List generic obligations for a Norwegian entity type

workflow.obligation-overview · List generelle forpliktelser for en norsk selskapsform

Hent det generelle settet med forpliktelser for en gitt selskapsform (AS, ENK, ANS, DA, NUF). Dette er bare malnivået: oppføringer med `tier_2_required: true` trenger kommersielle data for å vurderes per selskap, og Apier leverer ikke slike data i dag (delegeringsporten ble trukket tilbake 2026-10-21), så de vurderes til insufficient_data.

Intensjon
List the universal regulatory obligations (tax, reporting, insurance, registration) that apply to a Norwegian entity type, and identify which of those need Tier 2 commercial data to evaluate per-company.
Forventet resultat
Obligation template set: each entry names the obligation, category, frequency, required/conditionally/never applicability, a Norwegian condition string, tier_2_required flag, and the Lovdata legal reference.
Utløsende intensjon
“What obligations apply to a Norwegian aksjeselskap (AS)?”
Estimert tid
~150 ms · ingen autentisering

Steg

  1. 1

    Call GET /api/v1/public/obligations?entity_type=<AS|ENK|ANS|DA|NUF>. Use the `tier_2_required` flag to know which obligations evaluate to insufficient_data per company today.

    public.obligations → JSON envelope with data.entity_type, data.obligations[] (may be empty for ANS/DA/NUF), data.notes[], and _meta.served_from='static'.

Agentinstruksjoner

1. Call GET /api/v1/public/obligations?entity_type=<AS|ENK|ANS|DA|NUF> (no authentication).
2. Iterate data.obligations — an array of obligation templates.
3. For each obligation with tier_2_required === true, note that the paid /v1/company/{org}/obligations endpoint returns insufficient_data for it: the Tier 2 data it needs is not served (its delegation gate was withdrawn on 2026-10-21).
4. Obligations with required='never' are DELIBERATELY included so agents see they were considered and ruled out (e.g. revisor-plikt for ENK).
5. ANS, DA, and NUF currently return an empty obligations array with a notes entry — templates are not yet published.

Feilmoduser å planlegge for

  • invalid_entity_type
  • empty_template_set

Eksempelforespørsel

GET /api/v1/public/obligations?entity_type=AS

Reconcile a customer's filing history from the audit trail

workflow.reconcile-filing-history · Avstem en kundes innsendingshistorikk fra sporingsloggen

Hent forbrukerens egen sporingslogg for ett org_number over et datointervall, og bla med den ugjennomsiktige markøren (pagination.next_cursor) til den er tom. Nyttig for agenteiere som avstemmer aktivitet i etterkant, for operatører av AI-agenter som sporer hva agentene deres leser, og for en sporbar tidslinje ved tvister. Returnerer BARE rader som DIN forbruker har skrevet; innsyn på tvers av forbrukere er strukturelt umulig.

Intensjon
Reconstruct the activity timeline a single consumer's API key generated against one Norwegian organisation, optionally narrowed by action type or initiator class, for reconciliation, debugging, or dispute defense.
Forventet resultat
Ordered (timestamp DESC, id DESC) page of AuditLogEntry rows the consumer wrote for the org, each carrying correlation_id (joins to provenance_log / evaluation_snapshots / compliance_state_events), initiated_by classification, schema_version, and a scrubbed details JSONB.
Utløsende intensjon
“Show me every audit-log row my consumer wrote for org 999999999 in the last 90 days.”
Estimert tid
~250 ms · krever API-nøkkel

Steg

  1. 1

    Call GET /api/v1/company/{org}/audit with the consumer API key (read:audit scope). Iterate the page; if pagination.has_more, repeat with ?cursor=pagination.next_cursor.

    company.audit → JSON envelope with data.data[] (AuditLogEntry array), data.pagination.has_more, data.pagination.next_cursor (string or absent), the legacy data.pagination.next_before / next_before_id fields, and _meta with response_timestamp + response_hash.

Agentinstruksjoner

1. Ensure your API key has the read:audit scope (operator-issued via /v1/admin/keys).
2. Call GET /api/v1/company/<ORG_NUMBER>/audit?since=<ISO_FROM>&until=<ISO_TO>&limit=200 with the consumer API key.
3. Iterate data.data — each row is an AuditLogEntry. correlation_id joins to provenance_log / evaluation_snapshots / compliance_state_events from the same originating request.
4. If pagination.has_more is true, pass pagination.next_cursor back as ?cursor=<value> to fetch the next page (canonical). The legacy ?before=&before_id= tuple still works through the deprecation window (responses to it carry Deprecation/Sunset headers); if you use it, both parameters are required together.
5. To narrow further: ?action=<closed-enum> or ?initiated_by=<human|agent|cron|system|unknown>. Action enum is a closed list — anything outside the list is rejected at 400.
6. details.* values matching token / secret / password / bearer / authorization / jwt / api_key / private_key / credential / client_secret / refresh_token are auto-redacted to the literal string [REDACTED] at BOTH write and read time.
7. An empty array (data.data === []) for a valid (consumer, org) pair is returned as 200, not 404 — that prevents existence-leak across consumers.

Feilmoduser å planlegge for

  • auth_missing
  • scope_insufficient
  • validation_failed
  • audit_query_failed

Eksempelforespørsel

curl -H 'Authorization: Bearer <API_KEY>' 'https://www.apier.no/api/v1/company/999999999/audit?limit=50&initiated_by=agent'

Track historical changes for a customer company

workflow.track-changes · Følg historiske endringer for en kundevirksomhet

Hent alle endringshendelser for ett org_number fra endringsarkivet (innhenting fra Brreg pluss flere kilder: Altinn, Digdir og Norges Bank). Markørbasert paginering: send next_cursor tilbake som ?cursor= for neste side.

Intensjon
Subscribe (via polling) to changes affecting a Norwegian company, audit historical mutations, or reconstruct what Apier saw at a given time across all four upstream sources.
Forventet resultat
Page of change events (created/updated/deleted) ordered detected_at DESC, id DESC. Each row carries source_snapshot_id for joining to the response receipt, plus a derived observation_kind (first_observation = the archive's first sighting, value_change = a real observed transition). With entity_id supplied (this workflow's golden path) personal role-holder fields are included; without it, role-holder field rows AND whole-entity company created/deleted rows (their snapshots embed role-holder arrays) are withheld — intentionally, not as missing archive data — and personal_fields_withheld is true.
Utløsende intensjon
“Show me everything that changed for org_number 998877665 in the last 30 days.”
Estimert tid
~200 ms · krever API-nøkkel

Steg

  1. 1

    Call GET /api/v1/changes?source=brreg&entity_id={org_number}&from={iso_date} with the consumer API key (read:changes scope). Iterate the page; if pagination.has_more, repeat with ?cursor=pagination.next_cursor.

    changes.query → JSON envelope with data.data[] (PublicChangeRow array), data.pagination.has_more, data.pagination.next_cursor (string or null), and _meta with response_timestamp + response_hash.

Agentinstruksjoner

1. Ensure your API key has the read:changes scope (operator-issued via /v1/admin/keys).
2. Call GET /api/v1/changes with filters: source (brreg|altinn|digdir|norges_bank|nav|skatteetaten), entity_id, change_type (created|updated|deleted), from + to (RFC 3339).
3. Iterate data.data — each row is a created/updated/deleted event with before_value/after_value JSONB blobs, an RFC 6902 diff array, and a derived observation_kind (treat first_observation rows as the archive's first sighting of that field/entity, not a real-world change).
4. If pagination.has_more is true, pass pagination.next_cursor back as ?cursor=<value> to fetch the next page. Do NOT modify the cursor — it's HMAC-signed and tampered cursors return 400 CURSOR_INVALID.
5. correlation_id is intentionally not exposed; use source_snapshot_id to join back to provenance receipts.

Feilmoduser å planlegge for

  • auth_missing
  • scope_insufficient
  • cursor_invalid
  • validation_failed

Eksempelforespørsel

curl -H 'Authorization: Bearer <API_KEY>' 'https://www.apier.no/api/v1/changes?source=brreg&entity_id=998877665&from=2026-01-01T00:00:00Z'

Withdrawn (2026-10-21): validate a filing before submission

workflow.validate-filing · Trukket tilbake (2026-10-21): valider en innlevering før innsending

TRUKKET TILBAKE. Prøveinnsendingsmotoren bak denne arbeidsflyten leste delegeringsstatus fra Altinn (to av de fem kontrollene), og MVA-innsendingen den matet, er satt på vent. POST /api/v1/actions/execute svarer HTTP 410 med error_code CAPABILITY_WITHDRAWN på hvert kall, både prøveinnsending og kall i drift. Oppføringen blir stående så bufrede planleggere fortsatt finner den (en kontrakt som bare kan utvides). For selskapets registrerte signaturregler, bruk GET /api/v1/company/{org}/authority.

Intensjon
Tell an agent that filing validation and submission are not offered, and route it to the live company reads (status, roles, signing authority, obligations, deadlines) instead.
Forventet resultat
An HTTP 410 CAPABILITY_WITHDRAWN envelope with a bilingual explanation; no DryRunOutcome is produced.
Utløsende intensjon
“Can Apier validate or submit my MVA-melding? (No: withdrawn.)”
Estimert tid
~100 ms · krever API-nøkkel

Steg

  1. 1

    Withdrawn: POST /api/v1/actions/execute answers HTTP 410 CAPABILITY_WITHDRAWN before authentication, body parsing or any upstream call. Kept so the step resolves against the manifest id.

    actions.execute_dry_run → JSON error envelope: success false, error_code CAPABILITY_WITHDRAWN, explanation (summary / summary_en / fix_steps / fix_steps_en), retryable false, and _meta with response_timestamp + response_hash.

Agentinstruksjoner

1. Do not call POST /api/v1/actions/execute: it answers HTTP 410 CAPABILITY_WITHDRAWN on every call, with or without ?dry_run=true.
2. Read the error envelope's explanation (summary_en / fix_steps_en) and surface it to the operator; do not retry.
3. For the register's coded signing rules for the company, call GET /api/v1/company/<ORG_NUMBER>/authority (signaturrett and prokura from Brønnøysund). For what the company must do and when, call GET /api/v1/company/<ORG_NUMBER>/obligations and /deadlines.
4. Filing itself happens with the company's own credentials at Skatteetaten or Altinn, outside Apier.

Feilmoduser å planlegge for

  • capability_withdrawn

Eksempelforespørsel

Dry-run: POST /api/v1/actions/execute?dry_run=true with headers { Authorization: Bearer <KEY> } and body { org_number, action_type, period, payload }. Live-execute: POST /api/v1/actions/execute with headers { Authorization: Bearer <KEY>, Idempotency-Key: <UUID>, X-Approval-Token: <token> } and body { org_number, action_type: "mva_melding", period, payload }. Both modes require API-key auth via Authorization header.

Onboard a Norwegian client company from a single org number (KYB)

workflow.kyb-client-onboarding · Onboard en norsk kundevirksomhet fra ett organisasjonsnummer (KYB)

Sammensatt KYB-kjede (kjenn din virksomhet) i fem steg over selskapsoppslagene i drift: bekreft at selskapet finnes og les den registrerte statusen, les den registrerte signaturregelen, les det innsendte årsregnskapet, vurder forpliktelsene og utvid den konkrete fristkalenderen. Hvert steg svarer med `_meta.response_hash` og skriver en rad i provenance_log, så det samlede svaret har sporbar opprinnelse hele veien; stegene for verifisering og signaturrett kan i tillegg returnere et JWS-sertifikat som kan verifiseres frakoblet, via `?certificate=true`.

Intensjon
Onboard a Norwegian client company from a single organisation number: establish that it is real and active, the register's coded signing rules for the company, what its filed accounts show, which obligations apply, and when they fall due — one provenance-stamped answer per question.
Forventet resultat
A provenance-backed onboarding summary assembled from five responses: a pass/fail/unknown verification verdict (warn is reserved in the contract and not emitted today), a signing-authority classification with the named holders, the filed annual-accounts snapshot with key figures, the evaluated obligation catalogue, and the weekend/holiday-adjusted deadline calendar — each response carrying `_meta.response_hash` (joinable to provenance_log), with optional detached-JWS certificates from the verify and authority steps for offline re-verification.
Utløsende intensjon
“Onboard company 999999999 as a client — does it exist, what are its registered signing rules, and what does it owe when?”
Estimert tid
~2500 ms · krever API-nøkkel

Steg

  1. 1

    Call GET /api/v1/company/{org}/verify (optionally ?certificate=true) and gate the rest of the chain on data.verification_status — stop on 'fail', flag 'unknown' for manual review, continue on 'pass'.

    company.verify → JSON envelope with data.verification_status (pass/fail/unknown; warn is reserved in the vocabulary and not emitted today), data.signals (seven tri-state booleans), and _meta with response_hash; with ?certificate=true the data block is a detached-JWS certificate wrapping the same verdict.

  2. 2

    Call GET /api/v1/company/{org}/authority (optionally ?certificate=true) to read the company's registered signing rule before any binding onboarding step. Run it only after the step-1 verification gate: the classification covers signing arrangements and does not reflect bankruptcy or dissolution.

    company.authority → JSON envelope with data.classification (sole/joint/by_role/prokura_only/no_authority/unknown), data.signaturrett_holders, data.prokura_holders, and _meta with response_hash.

  3. 3

    Call GET /api/v1/company/{org}/accounts for the filed annual-accounts snapshot — treat has_filed_annual_accounts null as unknown, never as 'not filed'.

    company.accounts → JSON envelope with data.has_filed_annual_accounts (tri-state), data.last_accounts_year, data.key_figures (with explicit currency), and _meta with response_hash.

  4. 4

    Call GET /api/v1/company/{org}/obligations to evaluate every Rulebook obligation for the company — insufficient_data verdicts mark the rules that need Tier 2 data, which is not served.

    company.obligations → JSON envelope with data.obligations[] (one EvaluationResult per rule: applicable/not_applicable/insufficient_data), data.data_tier, and _meta with response_hash.

  5. 5

    Call GET /api/v1/company/{org}/deadlines to expand the applicable obligations into the concrete weekend/holiday-adjusted deadline calendar.

    company.deadlines → JSON envelope with data.deadlines[] (DeadlineEntry rows, due_at ascending, Europe/Oslo offsets), data.data_tier, and _meta with response_hash.

Agentinstruksjoner

1. Ensure you hold a consumer API key (Authorization: Bearer) with the read:brreg scope; ORG_NUMBER below is a 9-digit Norwegian organisation number.
2. Call GET /api/v1/company/<ORG_NUMBER>/verify. Branch on data.verification_status: 'fail' means the company is not active — stop onboarding and surface data.summary; 'unknown' means the status is indeterminate, or the company is active but no signing authority is visible in the open role data — continue, but flag it for manual review; 'pass' continues. 'warn' is reserved in the contract and not emitted today, so never branch on it as a live outcome. Append ?certificate=true when you want the verdict wrapped in an offline-verifiable detached-JWS certificate.
3. Only after the step-2 gate, call GET /api/v1/company/<ORG_NUMBER>/authority. The classification covers signing arrangements only; it does not reflect bankruptcy or dissolution, so it never resolves a step-2 verdict: a 'fail' has already stopped the chain, and an 'unknown' status stays unresolved and needs manual review before any binding action. Read data.classification (sole / joint / by_role / prokura_only / no_authority / unknown) and data.signaturrett_holders + data.prokura_holders as the registered signing arrangements, not as a determination of who may approve a particular binding action; request human review for action-specific authority. ?certificate=true is available here too.
4. Call GET /api/v1/company/<ORG_NUMBER>/accounts. data.has_filed_annual_accounts is tri-state (true / false / null=unknown — never coerce null to false); data.key_figures carries the latest filed year's figures with an explicit currency.
5. Call GET /api/v1/company/<ORG_NUMBER>/obligations. Each EvaluationResult is applicable / not_applicable / insufficient_data — treat insufficient_data as data that is unavailable (the Tier-2 delegation gate is withdrawn, so no delegation restores it), not as a no.
6. Call GET /api/v1/company/<ORG_NUMBER>/deadlines. Entries are already weekend/holiday-adjusted with Europe/Oslo offsets; sort order is due_at ascending.
7. Assemble the onboarding summary from the five data blocks. Keep each response's _meta.response_hash (and the step-2/3 certificates if requested) as the provenance trail for the decision.
8. Keyless rehearsal: the same five reads are served on the zero-auth sandbox mirror at GET /api/v1/sandbox/public/company/999999999/<verify|authority|accounts|obligations|deadlines> (one synthetic fixture company, no API key, IP rate-limited) and, with a consumer key or the apier_sandbox_test_<suffix> bearer, at /api/v1/sandbox/company/<ORG_NUMBER>/... for every org in the sandbox.fixture_pools lists of /workflows.json. Sandbox responses carry _meta.is_sandbox: true and never reach a government register, so rehearse the branching there before spending metered production reads.

Feilmoduser å planlegge for

  • org_not_found
  • auth_missing
  • auth_invalid_key
  • scope_insufficient
  • upstream_timeout

Eksempelforespørsel

curl -H 'Authorization: Bearer <API_KEY>' https://www.apier.no/api/v1/company/999999999/verify