For platforms · Signature + Authority

Read signing rules across a client portfolio

The job

You run an agent platform that handles many companies and need to read, per organisation, the register's coded signing rules for the company before a binding action, as the registers hold them.

Endpoint

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

Request

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

Response

{
  "success": true,
  "data": {
    "org_number": "999999999",
    "name": "Synthetic Test AS",
    "entity_type": "AS",
    "classification": "joint",
    "summary": "To personer må tegne selskapet i fellesskap.",
    "kombinasjon_available": true,
    "signaturrett_holders": [
      {
        "role": "Styreleder",
        "name": "Ola Nordmann"
      },
      {
        "role": "Daglig leder",
        "name": "Kari Nordmann"
      }
    ],
    "prokura_holders": [],
    "data_sources": [
      "brreg",
      "fullmakttjenesten"
    ],
    "resolved_at": "2026-06-16T12:00:00+02:00"
  },
  "_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"
  }
}

Run this call per client org number and read data.classification: sole, joint, by_role, prokura_only, no_authority or unknown. On joint, several people must approve; on unknown the answer is unresolved and needs a manual review.

Next steps

Build a dashboard grid: one row per client, colour-coded on the signing-authority classification.
Treat unknown as unresolved: have a person review the company before the agent proceeds.