Apier

Apier.no

Support

Get help with Maskinporten, Altinn 3, and apier.no integrations. Response time depends on plan — see the support policy below.

Driftstatus / Service status

Before contacting support, check whether there is a known incident: status.apier.no

Common issues

  • Maskinporten returns 401 Unauthorized

    Check that your MASKINPORTEN_KID matches the key pair registered on Samarbeidsportalen. Key rotation requires updating both the portal AND your Vercel/server environment variable.

  • My API key works in sandbox but not production

    Production keys (apier_live_) require a paid subscription and an active Maskinporten production client. Sandbox keys (apier_test_) only hit mock endpoints.

  • Altinn returns scope error / Tilgang mangler

    The requested scope has not been granted to your 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-org rate limits to protect upstream government APIs. Cache Maskinporten tokens (they are valid for 120 seconds) rather than fetching a new one per request. Contact support if your legitimate use case requires a higher limit.

  • Altinn 2 vs Altinn 3 — which endpoint should I use?

    Altinn 2 shuts 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 per-tier 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

Support policy

PlanResponse timeChannels
Developer / FreeBest effortEmail
Starter1 business dayEmail
Professional4 business hoursEmail
EnterprisePriority (per agreement)Email

For critical production incidents outside business hours, include URGENT in the subject line. We check these multiple times daily, including evenings and weekends.