Endpoint reference
Apier.no API contract, with the authoritative machine-readable spec at /openapi.json and browsable per-endpoint docs grouped by capability.
[Cite this as: Apier.no Docs v0.1.0 — last updated 2026-04-22]
The authoritative reference is /openapi.json; the
machine-readable contract is the single source of truth. The sidebar
mirrors the OpenAPI tag structure for browsable navigation.
Categories
- Public (Category A): zero-auth, rate-limited per IP. Discovery-first surface; agents can evaluate the API without creating an account.
- Company (Category B): API-key gated, per-API-key rate
limits, carries an audit trail. Every response embeds
_metawith the Rulebook version + data freshness. - Tools: small helpers (exchange rates, Altinn 2→3 migration bridge) that don't fit the obligations/deadlines/compliance domain model.
Today
The authoritative spec is live at
/openapi.json. Every /api/v1/* response also
advertises it via the HTTP
Link: </openapi.json>; rel="service-desc" header.
How do I configure an MCP client for Apier?
Client-by-client setup for ChatGPT, Claude Code, Claude Desktop, Cursor, VS Code, and the OpenAI and Azure agent runtimes, a connection check, troubleshooting, key rotation, and the full 21-tool reference.
Guides
Deep-dive walkthroughs covering obligations, signing authority, deadlines, and errors.