Rolling deadline calendar for a specific company
Returns the concrete per-period deadline calendar for a Norwegian organisation, keyed on the set of regulatory obligations that apply given the company's entity_type plus — when a Tier 2 delegation is in place — its commercial metrics. Thin plumbing on top of three pure libs: the Universal Rulebook evaluator produces EvaluationResult[] per company context, the Deadline Engine expands applicable obligations into concrete per-period DeadlineEntry rows with Europe/Oslo offsets and weekend + Norwegian-holiday adjustment. The horizon is a rolling window anchored on from_date (defaults to today in Europe/Oslo) and extending horizon_months into the future (default 12, valid range 1–60); entries are emitted for every period whose start falls inside the window, so MVA termin 6 (due February of the next calendar year) can legitimately appear on a request whose window ends in January. Tier 2 gating matters: when the caller has no active delegation, obligations whose applicability depends on a Tier 2 field (employee_count, annual_turnover, total_assets, mva_registered) short-circuit to insufficient_data at the evaluator and emit NO deadline entries — callers remediate via POST /api/v1/auth/system-user/delegate and then re-call this endpoint. filing_status on each entry is either upcoming / overdue derived from due_at vs from_date, filed when the compliance-state engine has observed a successful submission for that period, or unknown when no compliance-state lookup is available. Entries are sorted by due_at ASC (nulls last) per the Deadline Engine's determinism guarantee; the same (org_number, from_date, horizon_months) triple always produces the same array.
Request
- Base URL: https://www.apier.no
- URL: https://www.apier.no/api/v1/company/{org}/deadlines
- Auth: HTTP bearer
Path parameters
9-digit Norwegian organisation number (Brønnøysund-issued). Any other shape returns 400 VALIDATION_FAILED before the cache is touched.
Query parameters
Lower bound of the horizon — either a bare YYYY-MM-DD date or a full ISO 8601 timestamp with offset. Defaults to today in Europe/Oslo. The engine snaps this value to first-of-month in Oslo before expansion, so an obligation whose period starts earlier in the same month is still emitted. Invalid values return 400 VALIDATION_FAILED.
How many calendar months forward from from_date to expand. Default 12; valid range 1–60. A value outside the range returns 400 VALIDATION_FAILED. Five years is the hard cap — beyond that the underlying legal thresholds (Aksjeloven, MVA-forskriften) revise more often than the horizon is useful.
Response
Deadline calendar computed for the org. Deadlines are sorted by due_at ASC (nulls last) and deterministic across repeated calls over unchanged inputs.
Example response
{
"data": {
"deadlines": [
{
"obligation_id": "AMELDING_MONTHLY",
"period_label": "2026-01"
}
]
},
"_meta": {
"rulebook_version": "v1.0.0",
"source": "apier.no",
"data_source": "Brønnøysund Enhetsregisteret + Apier Universal Rulebook",
"schema_version": "1.0.0",
"legal_basis": "NLOD — public registry reuse",
"response_timestamp": "2026-04-24T12:00:00.000Z",
"response_hash": "sha256:0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef",
"source_snapshot_id": "brreg-2026-04-24T02:00:00.000Z",
"cost_nok": 0.5,
"wallet_remaining_nok": 9.5,
"spend_cap_remaining_nok": 12.5
}
}Changes
No recorded changes to this operation across all 1 revision of this API.