A permanent, no-signup test surface that mirrors the production request and response shapes against deterministic synthetic data, and never calls a government system. Use it to rehearse the full authenticated flow, including failures, before you go live. There are two ways in.
How to use the sandbox
1 · Public, zero-auth
The public mirror (/api/v1/sandbox/public/*) needs no key at all and serves org 999999999. Best for a first look at the response shapes.
2 · No-signup synthetic bearer
Pass Authorization: Bearer apier_sandbox_test_<uuid> to reach the eight non-public routes and the richer fixtures. The <uuid> suffix is your private, isolated session namespace; generate a fresh one per agent or run. Mock filings persist under your suffix for 15 minutes: the next read of /audit, /obligations or /summary with the same suffix and organization shows the Pending→Filed transition, marked _meta.session_merged: true.
Sandbox handler responses (success and simulated failure) are tagged _meta.is_sandbox: true, and so is the missing-auth 401 (whose fix_steps name the synthetic bearer); other pre-handler rejections (e.g. an invalid real key) may omit it. You can shape behaviour with deterministic knobs (?simulate_error= for the eight failure modes, ?simulate_latency= to pause a response, and ?mock_date= to pin the clock) and force filing outcomes with magic payload values. Every synthetic org, token, knob, and magic value lives in the fixtures reference.
Eleven reserved org numbers, each one deterministically returning a single documented company state on the authenticated read surface, the regulatory edge cases an agent must learn to handle. Pass the no-signup synthetic bearer and hit /api/v1/sandbox/company/<org>/verify (or /authority, /obligations). This table is generated from the same source as GET /api/v1/sandbox/fixtures.
Magic state fixtures
Org number
State
Entity
/verify
/authority
MVA
Obligations
999660010
Bankrupt (konkurs)
AS
fail
sole
yes
none (company is bankrupt)
999660029
Struck from register (slettet)
AS
fail
sole
no
none (company is deleted)
999660037
Forced liquidation (tvangsavvikling)
AS
fail
sole
yes
none (company is in forced liquidation)
999660045
No registered roles
AS
unknown
no_authority
yes
MVA-melding (bimonthly)
999660053
Not VAT-registered
AS
pass
sole
no
none (not MVA-registered)
999660061
Enkeltpersonforetak (ENK)
ENK
pass
sole
no
Skattemelding for næringsdrivende (annual)
999660088
Aksjeselskap (AS)
AS
pass
sole
yes
MVA-melding (bimonthly)
999660096
Registered <30 days ago
AS
pass
sole
yes
MVA-melding (bimonthly)
999660118
Joint signing authority
AS
pass
joint
yes
MVA-melding (bimonthly)
999660126
Prokura-only authority
AS
pass
prokura_only
yes
MVA-melding (bimonthly)
999660134
Slow response (by org number)
AS
pass
sole
yes
MVA-melding (bimonthly)
Live-surface synthetic org numbers
These are not sandbox fixtures; they are safe synthetic org numbers for the live production surface (real API key required), for when you need a test org outside the sandbox. The 999xxxxxxx range is reserved for synthetic testing and 123456789 is the docs-standard mock used across the OpenAPI manifest and capability examples. For sandbox calls, use the magic-state fixtures above; the full catalogue (reserved test orgs, the realistic graph, reserved error orgs, and more) lives in the fixtures reference.
Live-surface synthetic org numbers
Org number
Name
Entity
Data tier
Scenario
999111114
Synthetic AS with Tier 2 fixture data
AS
tier_1+2
AS with Tier 2 fixture data
999222226
Synthetic ENK Sole Proprietor
ENK
tier_1
ENK sole proprietor, no employees
999333338
Synthetic DA Partnership
DA
tier_1
DA partnership (delt ansvar)
123456789
Docs-standard mock org
NUF
tier_1
NUF (foreign branch)
999444008
Sandbox unknown-org placeholder
AS
tier_1
sandbox-unknown-org
999770002
Brattfjell Bygg og Anlegg AS
AS
tier_1
Bankruptcy in progress
999770010
Solnedgang Handel AS
AS
tier_1
Voluntary liquidation (under avvikling)
999770029
Fjordkanten Kafé AS
AS
tier_1
VAT deregistered (was registered)
999770037
Nordvik Snekkerservice
ENK
tier_1
ENK sole proprietor, zero employees
999770045
Tvillingfjell Eiendomsinvest AS
AS
tier_1
Disputed / ambiguous signatur
999770053
Gråsteinen Holding AS
AS
tier_1
Degraded / missing registry data
999770061
Vestkyst Distribusjon AS
AS
tier_1
Absorbed by merger
999770088
Vestkyst Logistikk AS
AS
tier_1+2
Recently merged and renamed
999770096
Balticum Bygg Norge NUF
NUF
tier_1
Foreign-owned branch (NUF)
999770118
Knoppskyting Teknologi AS
AS
tier_1
Newly registered, no filing history
999770126
Hvilende Fjelleiendom AS
AS
tier_1
Dormant but still registered
Named scenarios
Map a plain-language intent (“company under bankruptcy”, “prokura only”, “missed VAT deadline”) to a one-call recipe. Each scenario composes the magic-state orgs, deterministic knobs, and magic VAT values above into a copy-paste cURL plus the outcome to expect. Read scenarios use the no-signup synthetic bearer. The write scenarios rehearse a withdrawn flow against fixtures: they mint a deterministic sandbox approval token first, nothing reaches a government system, and the production write path they mirror answers 410 CAPABILITY_WITHDRAWN since 2026-10-21.
Company under bankruptcy
read
A limited company has gone bankrupt (konkurs) and I must detect it before I rely on it as a counterparty.
Expect each deadline's temporal status re-derived against the pinned Europe/Oslo date: the 2027-05-10 MVA deadline reads overdue on 2027-05-11 — move as_of earlier to see it upcoming. The deadline DATES never move (deterministic fixtures); as_of is bounded to [2020-01-01, today + 2 years], out-of-bounds returns 422. ?mock_date=YYYY-MM-DD recomputes this read the same way (wider bounds 2000..2100, malformed returns 400, no test bearer needed; as_of wins when both are present) — and it also drives the write path, where POST /actions/execute computes filed_late against the pinned date (see the late-VAT-filing scenario).
Late VAT filing
write
I am filing a VAT return for a period whose deadline has already passed and want the late-filing flag on the receipt.
POST/api/v1/sandbox/actions/execute
Recipe
# 1 · mint the deterministic approval token for (org, action)
curl -X POST https://www.apier.no/api/v1/sandbox/auth/approval-token \
-H "Authorization: Bearer apier_sandbox_test_$(uuidgen)" \
-H "Content-Type: application/json" \
-d '{"org_number":"999000001","action":"mva_melding"}'
# → { "data": { "approval_token": "sandbox-approval-…" } }
# 2 · execute with that token — a period before the sandbox clock forces the late-filing flag
curl -X POST "https://www.apier.no/api/v1/sandbox/actions/execute" \
-H "Authorization: Bearer apier_sandbox_test_$(uuidgen)" \
-H "Idempotency-Key: $(uuidgen)" \
-H "Content-Type: application/json" \
-d '{"org_number":"999000001","action":"mva_melding","payload":{"period":"2020-01","total_revenue_nok":500000},"approval_token":"PASTE_FROM_STEP_1"}'
Expect 200 accepted with filed_late: true (the period precedes the effective sandbox now).
Note Two calls: mint an approval token for (org, action), then execute with it. The token is deterministic per (org, action).
Missed VAT deadline (clock pinned past the deadline)
write
I want to rehearse deadline-passed handling by advancing the sandbox clock beyond a filing period's deadline.
POST/api/v1/sandbox/actions/execute
Recipe
# 1 · mint the deterministic approval token for (org, action)
curl -X POST https://www.apier.no/api/v1/sandbox/auth/approval-token \
-H "Authorization: Bearer apier_sandbox_test_$(uuidgen)" \
-H "Content-Type: application/json" \
-d '{"org_number":"999000001","action":"mva_melding"}'
# → { "data": { "approval_token": "sandbox-approval-…" } }
# 2 · execute with that token — ?mock_date advances now to 2030-06-15, past the 2030-04 period
curl -X POST "https://www.apier.no/api/v1/sandbox/actions/execute?mock_date=2030-06-15" \
-H "Authorization: Bearer apier_sandbox_test_$(uuidgen)" \
-H "Idempotency-Key: $(uuidgen)" \
-H "Content-Type: application/json" \
-d '{"org_number":"999000001","action":"mva_melding","payload":{"period":"2030-04","total_revenue_nok":500000},"approval_token":"PASTE_FROM_STEP_1"}'
Expect 200 accepted with filed_late: true — ?mock_date pins now after the period, so the deadline reads as missed.
Note Two calls: mint an approval token for (org, action), then execute with it. The token is deterministic per (org, action).
Government rejects the filing
write
I need to see how a government-side validation rejection surfaces so my agent can recover from it.
POST/api/v1/sandbox/actions/execute
Recipe
# 1 · mint the deterministic approval token for (org, action)
curl -X POST https://www.apier.no/api/v1/sandbox/auth/approval-token \
-H "Authorization: Bearer apier_sandbox_test_$(uuidgen)" \
-H "Content-Type: application/json" \
-d '{"org_number":"999000001","action":"mva_melding"}'
# → { "data": { "approval_token": "sandbox-approval-…" } }
# 2 · execute with that token — total_revenue_nok 99999999 forces the government 422
curl -X POST "https://www.apier.no/api/v1/sandbox/actions/execute" \
-H "Authorization: Bearer apier_sandbox_test_$(uuidgen)" \
-H "Idempotency-Key: $(uuidgen)" \
-H "Content-Type: application/json" \
-d '{"org_number":"999000001","action":"mva_melding","payload":{"total_revenue_nok":99999999},"approval_token":"PASTE_FROM_STEP_1"}'
Expect 422 GOVERNMENT_VALIDATION_REJECTED with a Skatteetaten-shaped TOTALS_DO_NOT_RECONCILE upstream envelope.
Note Two calls: mint an approval token for (org, action), then execute with it. The token is deterministic per (org, action).
Edge validation rejection (zero revenue)
write
I want to see Apier reject a malformed filing at its own edge, before it ever reaches the government.
POST/api/v1/sandbox/actions/execute
Recipe
# 1 · mint the deterministic approval token for (org, action)
curl -X POST https://www.apier.no/api/v1/sandbox/auth/approval-token \
-H "Authorization: Bearer apier_sandbox_test_$(uuidgen)" \
-H "Content-Type: application/json" \
-d '{"org_number":"999000001","action":"mva_melding"}'
# → { "data": { "approval_token": "sandbox-approval-…" } }
# 2 · execute with that token — total_revenue_nok 0 is rejected at Apier's edge
curl -X POST "https://www.apier.no/api/v1/sandbox/actions/execute" \
-H "Authorization: Bearer apier_sandbox_test_$(uuidgen)" \
-H "Idempotency-Key: $(uuidgen)" \
-H "Content-Type: application/json" \
-d '{"org_number":"999000001","action":"mva_melding","payload":{"total_revenue_nok":0},"approval_token":"PASTE_FROM_STEP_1"}'
Expect 400 VALIDATION_FAILED at Apier's edge — a declared MVA-melding cannot report zero total revenue.
Note Two calls: mint an approval token for (org, action), then execute with it. The token is deterministic per (org, action).
Try it — public endpoints
Zero-auth, permanently rate-limited per-IP at 1000 req/min (Category A). Every cURL runs against the live production API.
Norwegian business deadlines for a given calendar year
Every deadline is ISO 8601 with the Europe/Oslo offset baked in. `adjusted_from` is non-null when the legal date fell on a weekend or holiday, so agents do not need to reimplement Oslo business-day math.
Generic Norwegian business obligations by entity type
`tier_2_required: true` marks obligations that would need Tier 2 commercial data for a company-specific verdict. Tier 2 data is not served (the Altinn delegation gate was withdrawn on 2026-10-21), so the `/company/*` endpoints return `insufficient_data` for them.
Requirements in force for a Norwegian company type on a date
{
"success": true,
"data": {
"entity_type": "AS",
"date": "2026-03-01",
"requirements": [
{
"requirement_id": "MVA_REGISTRATION_THRESHOLD",
"version": 1,
"legal_reference": "Merverdiavgiftsloven § 2-1",
"source_url": "https://lovdata.no/lov/2009-06-19-58/§2-1",
"entity_types": ["AS", "ENK", "NUF", "ANS", "DA"],
"preconditions": [
{ "field": "annual_turnover", "operator": "gt", "value": 50000, "data_tier": "tier_2" }
],
"obligations": [
{
"obligation_type": "mva_registration",
"description": "Selskapet må registreres i Merverdiavgiftsregisteret når avgiftspliktig omsetning overstiger 50 000 kr i en 12-månedersperiode.",
"frequency": "one_time",
"deadline_rule": "mva_registration_on_threshold_crossed",
"legal_basis": "Merverdiavgiftsloven § 2-1"
}
],
"evidence": [
{
"fact": "annual_turnover",
"source_id": "brreg_regnskap",
"max_age_days": null,
"how_recent": "The latest annual accounts filed with Regnskapsregisteret; state the accounting year used.",
"data_tier": "tier_2"
}
],
"effective_from": "2023-12-31T23:00:00.000Z",
"effective_to": null,
"last_reviewed": "2026-04-20T14:04:11.605713+00:00"
}
],
"coverage": {
"recorded_from": "2026-04-20",
"before_recording": true,
"note": "Answered from the Rulebook versions Apier has recorded, by each version's stated effective dates. Apier began recording Rulebook versions on the date in recorded_from; for an earlier date the answer shows the versions then stated as in force, not a reconstruction of older law."
},
"notice": "Lists the requirements in force for this company type on the date and the facts an agent checks before acting. It does not say whether any company meets a requirement, is obliged by it or may act."
},
"_meta": {
"rulebook_version": "1.0.0",
"data_freshness": "2026-04-20T14:04:11.605713+00:00",
"last_verified": "2026-04-20T14:04:11.605713+00:00",
"source": "apier.no",
"data_source": "Apier Universal Rulebook (versioned)",
"legal_basis": "NLOD — public registry reuse",
"schema_version": "1.0.0"
}
}
`preconditions` are listed, never evaluated: nothing here says whether a company meets a requirement. `evidence` names the fact to check, its source and how recent it must be; `coverage.before_recording` flags a date before Apier began recording Rulebook versions.
Bulk company status for up to 100 organisation numbers
Illustrative shape: the synthetic 999-range numbers above resolve `not_found` against the live registry, so run the cURL with your own portfolio to see populated rows. Notice `lookup_status` per row (a failed lookup never fails the batch), the tri-state booleans where `null` means genuinely unknown, and that NO role-holder fields (signaturrett/prokura) exist on this keyless surface.
Published daily Merkle anchors over the company snapshot archive
Newest day first. `tsa_provider` and `tsa_obtained_at` are `null` while the RFC 3161 timestamp token is still pending (the daily job retries). `tsa_tokens` lists every attached token in attach order: the first, then a second from a different timestamp authority; an older anchor may still list one while the daily job back-fills it. In this sample the second `tsa_tokens` entry is illustrative. A `chain_status` of `not_initialised` with an empty `anchors` list means the chain has not started in that environment, not that it is unavailable. A quiet day still gets a row with `leaf_count: 0`, so a missing date after genesis always means a failure.
{
"success": true,
"data": {
"entries": [],
"head": null,
"next_after_seq": null,
"log_status": "active",
"chain": {
"algorithm": "sha256-chain-v1",
"genesis_prev_chain_hash": "0000000000000000000000000000000000000000000000000000000000000000",
"formula": "chain_hash = sha256_hex(utf8(prev_chain_hash + \":\" + seq + \":\" + kind + \":\" + entry_hash)); prev_chain_hash of seq 1 is 64 zeros; for kind receipt, entry_hash = sha256_hex(utf8(receipt signature))"
},
"anchors": []
},
"_meta": {
"rulebook_version": "1.0.0",
"data_freshness": "1970-01-01T00:00:00.000Z",
"last_verified": "1970-01-01T00:00:00.000Z",
"source": "apier.no",
"data_source": "Apier public receipt log (hash chain)",
"legal_basis": "Derived hash material — no personal data on this surface",
"schema_version": "1.0.13"
}
}
An entry carries `seq`, `kind` (`receipt`), `entry_hash` (SHA-256 hex of the UTF-8 receipt signature), `prev_chain_hash`, `chain_hash` and `logged_at`. Page with `after_seq` set to `next_after_seq`; look one receipt up with `entry_hash`. `log_status: not_initialised` means the log has not started in that environment.
{
"success": true,
"data": {
"runs": [
{
"company": "Eksempel Teknologi AS",
"org_number": "999999999",
"ai_product": "Claude",
"model": "Sonnet 5.5",
"run_date": "2026-11-05",
"task": "company_verification",
"task_label": { "en": "Company verification", "nb": "Selskapsverifisering" },
"result": "passed",
"cost_nok": "1.50",
"tool_calls": 3,
"page_url": {
"en": "https://www.apier.no/case-studies/claude-eksempel-teknologi-as",
"nb": "https://www.apier.no/no/kasusstudier/claude-eksempel-teknologi-as"
},
"share_url": "https://claude.ai/share/00000000-0000-4000-8000-000000000000",
"evidence_pack_url": "https://www.apier.no/case-studies/claude-eksempel-teknologi-as/evidence-pack.json",
"evidence_pack_sha256": "0000000000000000000000000000000000000000000000000000000000000000",
"evidence_pack_bytes": 12542,
"receipt_log": {
"seq": 1,
"entry_hash": "1111111111111111111111111111111111111111111111111111111111111111",
"url": "https://www.apier.no/api/v1/public/receipt-log?entry_hash=1111111111111111111111111111111111111111111111111111111111111111"
},
"anchor": {
"date": "2026-11-05",
"merkle_root": "2222222222222222222222222222222222222222222222222222222222222222",
"url": "https://www.apier.no/api/v1/public/anchors"
},
"source_url": "https://data.brreg.no/enhetsregisteret/api/enheter/999999999"
}
],
"count": 1,
"generated_at": "2026-11-05T17:11:00.000Z"
},
"_meta": {
"rulebook_version": "1.0.0",
"data_freshness": "2026-11-05T17:11:00.000Z",
"last_verified": "2026-11-05T17:11:00.000Z",
"source": "apier.no",
"data_source": "Apier published case studies",
"legal_basis": "Company and AI product names from published runs — no personal data on this surface",
"schema_version": "1.0.13"
}
}
A run carries the company and its organisation number, the AI product and model, `task` (a closed label with `task_label` in English and bokmål), `result` (`passed`, `partly_passed` or `failed`), `cost_nok` as a decimal string, and the links to check it: the run page in both languages, the shared conversation, the evidence pack file with its SHA-256 and size, the receipt log entry, the daily anchor and the register's record. No person is named. In this sample the run, its hashes and its links are illustrative; the live endpoint lists the published runs.
Notices when a cited law or regulation section changes
A notice says only that the SHA-256 of a cited section moved: read the section on lovdata.no and the requirement with GET /api/v1/public/requirements. `limit` counts document versions; page with `after_id` set to `next_after_id`. `feed_status: not_initialised` means the Lovdata version table is not migrated in that environment. Webhook subscribers whose filter names `entity_type: "law_section_changed"` receive the same notices.
Inclusion proof from one snapshot leaf to its daily anchor
`leaf` is the RFC 6962 leaf hash: SHA-256 over 0x00 and the canonical JSON of `content_hash`, `first_observed_at` and `org_number`. Hash it with each `sibling` in order (0x01 prefix, sibling on the side `position` names) and compare with `merkle_root`.
Whether an agent key is active, expired or revoked, and its scopes
{
"success": true,
"data": {
"agent_key_id": "AbytHX3qdo_wy0RUb8u-rdG684R1zH71kZUBdz20TUk",
"alg": "Ed25519",
"status": "active",
"scopes": ["read:brreg", "read:rulebook"],
"expires_at": "2027-11-14T12:00:00.000Z"
},
"_meta": {
"rulebook_version": "1.0.0",
"source": "apier.no",
"data_source": "Apier agent key registry",
"legal_basis": "Key state only — no owner or account data on this surface",
"schema_version": "1.0.13"
}
}
`status` is `active`, `expired` or `revoked`; only an active key can use its `scopes`. An unknown `key_id` is a 404 NOT_FOUND, so a key that never existed and a revoked one are told apart.
{
"success": true,
"data": {
"checked_at": "2026-10-31T06:00:00.000Z",
"window_days": 30,
"sources": [
{
"source": "norges_bank_exchange_rates",
"name": "Norges Bank, exchange rates",
"source_url": "https://data.norges-bank.no/api/",
"health_status": "verified",
"last_success_at": "2026-10-30T08:00:24.381Z",
"last_attempt_at": "2026-10-30T08:00:24.381Z",
"lag_seconds": 79175,
"max_lag_seconds": 172800,
"outages": [],
"coverage_start": "2026-07-30T08:00:21.000Z",
"licence": {
"name": "Norges Bank, opphavsrett (kopiering tillatt når Norges Bank oppgis som kilde)",
"attribution": "Kilde: Norges Bank",
"url": "https://www.norges-bank.no/Opphavsrett/",
"derived_by_apier": []
}
}
]
},
"_meta": {
"rulebook_version": "1.0.0",
"data_freshness": "2026-10-31T06:00:00.000Z",
"last_verified": "2026-10-31T06:00:00.000Z",
"source": "apier.no",
"data_source": "Apier fetch and schedule records",
"legal_basis": "Operational records about public sources; no personal data on this surface",
"schema_version": "1.0.13"
}
}
Omit `source` for every listed source. `lag_seconds` is the time since the last successful fetch; past `max_lag_seconds` the source is `stale`. `outages` lists the runs of failed fetches in the last 30 days, with `ongoing: true` while the newest fetch is still failing. `coverage_start` is the first recorded successful fetch: Apier claims nothing about a source from before it.
Official Norges Bank NOK exchange rate for a currency and date
`date` is the actual publication day Norges Bank resolved the rate from; on weekends/holidays it falls back to the previous banking day and `requested_date` records what you originally asked for.
{
"success": true,
"data": {
"deprecation_deadline": "2026-06-19T23:59:59+02:00",
"timezone": "Europe/Oslo",
"days_remaining": 0,
"deadline_passed": true,
"entry": {
"altinn2_code": "A0208",
"altinn2_name_nb": "Merverdiavgiftsmelding",
"altinn3_code": "skd/mva-melding-innsending-v1",
"altinn3_name_nb": "MVA-melding innsending (Altinn 3-app)",
"redirect_url": null,
"service_owner": "Skatteetaten",
"migration_notes_nb": "MVA-meldingen sendes via Altinn 3-appen skd/mva-melding-innsending-v1 på https://skd.apps.altinn.no. Skatteetaten tilbyr en valideringstjeneste før innsending. Virksomheten leverer selv med egne legitimasjoner; Apier leverer ingen MVA-melding.",
"migration_notes_en": "The VAT return is submitted via the Altinn 3 app skd/mva-melding-innsending-v1 at https://skd.apps.altinn.no. Skatteetaten offers a validation service before submission. The company files it with its own credentials; Apier submits no VAT return.",
"verified": true
}
},
"_meta": {
"rulebook_version": "1.0.0",
"data_freshness": "2026-05-26T00:00:00.000Z",
"last_verified": "2026-11-07T06:07:20.781Z",
"source": "DigDir",
"schema_version": "1.0.0",
"served_from": "static"
}
}
Omit `altinn2_code` to receive the full `mappings` array. The deadline (2026-06-19T23:59:59+02:00 Europe/Oslo) has passed, so `deadline_passed` is `true` and `days_remaining` is `0`; agents should branch on the boolean, not reimplement the date math.
Every authenticated surface is listed with its `auth`, `tier_minimum`, and OpenAPI operation id. Parse this instead of hard-coding endpoint lists in agent prompts.
{
"success": true,
"data": {
"dimensions": [
{
"dimension": "authentication",
"apier": "Consumers authenticate with an API key over HTTPS. Apier reads open Brønnøysund registry data with its own credentials and brokers no government access on a consumer's behalf.",
"direct_integration": "The integrator registers their own Maskinporten client, manages an asymmetric key pair, and implements the signed-JWT token exchange for each government scope they need."
},
{
"dimension": "delegation_and_authority",
"apier": "Registered signature and prokura roles from the Brønnøysund registers are exposed through normalised endpoints with a single response envelope. Altinn delegation state is not read or served (withdrawn 2026-10-21).",
"direct_integration": "The integrator queries the Brønnøysund role registers themselves and, where their own integration needs Altinn rights, manages those with their own Altinn credentials."
},
{
"dimension": "audit_trail",
"apier": "API activity is recorded in an append-only audit log, and every response carries provenance metadata (response hash and wire timestamp) for later reconstruction.",
"direct_integration": "Consumer-side audit logging is the integrator's responsibility; the government APIs do not provide one on the caller's behalf."
},
{
"dimension": "legal_grounding",
"apier": "Obligation and deadline answers are produced by a versioned rulebook whose rules carry references to the underlying regulations, and responses state which rulebook version produced them.",
"direct_integration": "The integrator maps regulations to API behaviour themselves and tracks regulatory changes on their own."
},
{
"dimension": "error_handling",
"apier": "Upstream errors are normalised to one structured error format with machine-readable codes, an explanation, and remediation steps.",
"direct_integration": "Each government API surfaces its own error format; the integrator implements per-API error mapping and retry handling."
},
{
"dimension": "deadline_intelligence",
"apier": "Regulatory deadlines are computed in Europe/Oslo time with weekend and Norwegian public-holiday adjustment, versioned by the rulebook.",
"direct_integration": "Deadline rules must be implemented and maintained by the integrator from the published regulations; the government APIs do not compute them."
},
{
"dimension": "cross_agency_orchestration",
"apier": "One API surface spans Brønnøysund, Altinn, Skatteetaten, and NAV data behind a common envelope and a single authentication model.",
"direct_integration": "Each agency is a separate integration with its own authentication, schemas, and lifecycle."
},
{
"dimension": "maintenance_burden",
"apier": "Upstream schema and policy changes are monitored by Apier and surfaced through an append-only change archive; the consumer response contract is append-only.",
"direct_integration": "The integrator monitors each agency's changelogs and migration timelines (for example the Altinn 2 to Altinn 3 transition) and updates their integration accordingly."
},
{
"dimension": "time_to_first_call",
"apier": "Public endpoints and a zero-auth sandbox work without any government onboarding; company-data endpoints require an API key only.",
"direct_integration": "A first production call requires Maskinporten client registration plus the relevant government scope or delegation grants before any data is returned."
}
],
"methodology": "Qualitative comparison based on Apier product documentation and the publicly documented integration requirements for the Norwegian government APIs (Maskinporten, Altinn, Brønnøysund Register Centre, Skatteetaten). Quantitative performance claims (success rates, latency) are intentionally omitted until they can be backed by measured live telemetry.",
"source": [
"Apier product documentation and OpenAPI specification",
"Public Norwegian government integration documentation (Digdir/Maskinporten, Altinn, Brønnøysund Register Centre, Skatteetaten)"
],
"last_updated": "2026-10-21T00:00:00.000Z"
},
"_meta": {
"rulebook_version": "1.0.0",
"data_freshness": "2026-10-21T00:00:00.000Z",
"last_verified": "2026-10-21T00:00:00.000Z",
"source": "apier.no internal comparison",
"served_from": "static",
"schema_version": "2.0.0"
}
}
Designed to be parsed rather than rendered; each dimension carries one factual statement per column so agents can weigh Apier against building the direct integration at planning time. The methodology and source fields state the comparison basis on the wire.
Your live request log
Company read calls you make with a Bearer apier_sandbox_test_<suffix> bearer (the /company/<org>/* routes, plus any rate-limit 429 the sandbox wrapper emits) are captured in a private per-suffix log: the last 50 request/response pairs, kept for 15 minutes. The sandbox write loop (plan, approval-token, execute; a fixture rehearsal of a withdrawn production flow) is not captured today beyond such a 429. Type your suffix below to read it back (or fetch it directly: GET /api/v1/sandbox/sessions/<suffix>/log with the same bearer). Only your own bearer can read your log; bearer strings are never stored.
Sandbox test checklist
The end-to-end sandbox rehearsal, as a check-off list, from fetching the fixtures table to injecting an infrastructure failure and time-traveling a deadline. Check-off state is in-page only and resets on reload.
0 / 7 done
Frequently asked questions
Do I need an account or an API key to use the sandbox?
No. The public mirror under /api/v1/sandbox/public/* needs no key at all. For the other sandbox routes, pass Authorization: Bearer apier_sandbox_test_<uuid> with a UUID you generate yourself; no sign-up is involved.
Does the sandbox call Altinn, Brønnøysund or Skatteetaten?
No. The sandbox answers from deterministic synthetic data and never calls a government system, so a sandbox filing never reaches a real agency.
How do I test error handling in the sandbox?
Add ?simulate_error= for one of the eight failure modes, ?simulate_latency= to pause a response, or ?mock_date= to pin the clock. Magic payload values force filing outcomes. The fixtures reference lists every option.
How can I tell a sandbox response from a production one?
Sandbox handler responses, including simulated failures, carry _meta.is_sandbox: true.