Denne siden finnes foreløpig bare på engelsk. Innholdet nedenfor vises derfor på engelsk.
Apier.no
Support
Get help with your apier.no integration: company status, signing rules, obligations and API keys. Response time depends on plan; see the support policy below.
Service status
Before contacting support, check whether there is a known incident on the status page (driftstatus): status.apier.no
Common issues
A call returns MASKINPORTEN_AUTH_FAILED Status: Withdrawn
You need no Maskinporten client, certificate or key to use Apier, and Apier brokers no Maskinporten access for you: the company reads come from open public registers, and your integration authenticates to Apier with one API key. The surfaces that called Maskinporten were withdrawn on 2026-10-21 and answer 410
CAPABILITY_WITHDRAWN.MASKINPORTEN_AUTH_FAILEDstays in the error catalogue and the sandbox can simulate it. If a production call returns it, do not retry in a loop: send theX-Correlation-IDto Apier support.My API key works in sandbox but not production
Real API keys (prefixed
apr_, e.g.apr_free_on the free tier) work on both sandbox and production routes. The zero-signup synthetic sandbox bearer (apier_sandbox_test_) is accepted only on sandbox routes and is rejected on production.Altinn returns a scope error Status: Withdrawn
This error comes from Altinn, not from Apier: Apier makes no Altinn call on your behalf, and the surfaces that did were withdrawn on 2026-10-21. Altinn shows it as «Tilgang mangler» when the requested scope has not been granted to your own Maskinporten client. Scope approvals are managed on Samarbeidsportalen and may take days to weeks depending on the scope owner (Digdir, Altinn, Skatteetaten, NAV).
Rate limit exceeded
apier.no enforces per-minute and per-organisation rate limits. Read your key's ceiling and the per-key reset time from the X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset response headers. After a 429, wait the number of seconds in the Retry-After header before retrying. Contact support if your legitimate use case requires a higher limit.
Altinn 2 vs Altinn 3 — which endpoint should I use?
Altinn 2 shut down June 19, 2026. All new integrations should use Altinn 3 endpoints. See our migration guide at /use-cases/altinn-migration.
My webhook / integration stopped working after a Digdir update
Government APIs change without always providing advance notice. Check status.apier.no for known incidents. If not listed, email support@apier.no with your org number and the error response body.
Contact support
Email us at support@apier.no.
Response times vary by plan; see the support policy table below for the targets. All replies are sent Monday–Friday, Oslo time.
Please include in your email:
- — Your organisation number
- — The API endpoint you called
- — The full error response (redact your API key)
- — Approximate time of the incident (Oslo timezone)
Documentation
- /docs — API reference
- /use-cases/altinn-migration — Altinn 3 migration guide
- /trust — Security and compliance
Support policy
| Plan | Response time | Channels |
|---|---|---|
| Wallet account (pay as you go) | Best effort | |
| Existing Starter subscription | 1 business day | |
| Existing Professional subscription | 4 business hours | |
| Existing Enterprise subscription | Priority (per agreement) |
No new subscriptions are sold. An existing subscription keeps its response target until the end of its current billing period; after that the account is a wallet account.
For critical production incidents outside business hours, include URGENT in the subject line. We check these multiple times daily, including evenings and weekends.