For platforms · Obligations + Deadlines

Deadline monitoring across many clients

The job

You run a platform — or a regnskapsbyrå — that must surface upcoming deadlines for many companies in one view, computed correctly in Oslo time.

Endpoint

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

Request

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

Response

{
  "success": true,
  "data": {
    "org_number": "999999999",
    "entity_type": "AS",
    "data_tier": "tier_1",
    "deadlines": [
      {
        "obligation_id": "AARSREGNSKAP_AS",
        "obligation_name": "årsregnskap",
        "period_label": "2026",
        "due_at": "2027-07-31T23:59:59+02:00",
        "submission_window_closes": "2027-07-31T23:59:59+02:00",
        "adjusted_for": "none",
        "filing_status": "upcoming",
        "data_tier_required": "tier_1"
      }
    ]
  },
  "_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"
  }
}

Each deadlines[] entry is already weekend/holiday-adjusted (adjusted_for says how). due_at is ISO 8601 with the Oslo offset — use it directly, do not compute time zones yourself.

Next steps

Call the endpoint per client org number and merge into one timeline, sorted by due_at.
For an event-driven alternative to polling, subscribe to the change archive (see Annual Accounts Monitor).