Job recipe · Company Verification

Verify a company before onboarding

The job

You need to confirm that a Norwegian company exists, is active, and is safe to act for — before you onboard a customer or run a transaction.

Endpoint

GET /api/v1/company/{org}/verify

Request

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

Response

{
  "success": true,
  "data": {
    "org_number": "999999999",
    "name": "Synthetic Test AS",
    "entity_type": "AS",
    "verification_status": "pass",
    "signals": {
      "is_active": true,
      "not_bankrupt": true,
      "not_under_dissolution": true,
      "not_forcibly_dissolved": true,
      "has_signing_authority_defined": true,
      "has_filed_annual_accounts": true,
      "mva_registered": true
    },
    "summary": "Organisasjonen er registrert og aktiv, med definert signaturrett.",
    "signing_authority_summary": "Styreleder",
    "last_accounts_year": 2024,
    "municipality": "Oslo"
  },
  "_meta": {
    "rulebook_version": "1.0.0",
    "data_freshness": "2026-06-16T06:00:00.000Z",
    "last_verified": "2026-06-16T06:00:00.000Z",
    "source": "apier.no",
    "schema_version": "1.0.0",
    "data_source": "Brønnøysund Enhetsregisteret",
    "legal_basis": "NLOD — public registry reuse"
  }
}

Branch on data.verification_status for the overall verdict, and inspect data.signals for the individual signal. A signal can be null — that means unknown, never a silent “no”.

Next steps

If the company passes, resolve who can sign for it with the Signature + Authority recipe.
Read _meta to surface the data source and freshness in your own UI.