---
title: "List your signed delegation receipts — proof of fullmakt lifecycle events"
method: GET
path: "/api/v1/fullmakt/receipts"
tags: ["Fullmakt"]
---

# List your signed delegation receipts — proof of fullmakt lifecycle events

`GET /api/v1/fullmakt/receipts`

## Request

- Base URL: `https://www.apier.no`
- URL: `https://www.apier.no/api/v1/fullmakt/receipts`
- Auth: HTTP bearer

Consumer-scoped, keyset-paginated list of the SIGNED DELEGATION RECEIPTS the fullmakt routes emitted for YOUR consumer — the retrieval surface for cryptographic proof of fullmakt lifecycle events (delegation_granted from POST /v1/fullmakt/request, delegation_revoked from POST /v1/fullmakt/revoke). Use it when the original 201/200 response is gone: each entry's `receipt` object is the COMPLETE signed payload (every signed field plus the HMAC-SHA256-v1 signature) — verifiable by Apier (the HMAC secret never leaves the server; the receipt is Apier's attestation, not an offline consumer-verifiable signature). Nothing here widens disclosure — every listed field was already returned to this same consumer on the emitting response, and the HMAC secret never leaves the server, so returning the signature discloses nothing. Cross-tenant isolation is structural: only receipts whose consumer_id matches the authenticated API key's consumer are ever listed. Newest first; pass `pagination.next_before` and `pagination.next_before_id` back as `?before=` and `?before_id=` (a tuple — both or neither) for the next page. Supports conditional GET: every 200 carries a strong SHA-256 `ETag` (with `Cache-Control: private, max-age=60` and `Vary: Authorization`), and a request whose `If-None-Match` matches returns `304 Not Modified` with no body.

## Query parameters

- `limit` integer
- `cursor` string
- `before` string, date-time
- `before_id` string, uuid

## Headers

- `If-None-Match` string

## Response `200`

The caller's delegation receipts, newest first. An empty `data.receipts` is a valid state (no fullmakt lifecycle events recorded yet), never an error.

- object
  - `success` true, required
  - `data` object, required
    - `receipts` object[], required: Newest-first page of the caller's OWN signed delegation receipts. Empty array when the consumer has no receipts yet — a valid state, never an error.
      - `id` string, uuid, required: fullmakt_receipts row id — the keyset tiebreak (NOT the signed receipt_id, which lives inside `receipt`). Pass back as `before_id`.
      - `created_at` string, date-time, required: Row persistence instant — the keyset cursor timestamp. Pass back as `before`.
      - `receipt` SignedDelegationReceipt, required: HMAC-signed fullmakt delegation receipt — cryptographic proof that at `signed_at`, consumer `consumer_id` obtained (`delegation_granted`) or revoked (`delegation_revoked`) a scoped systembruker delegation for `org_number`. Signed through the SAME HMAC-SHA256-v1 core as the filing `SignedReceipt` (one crypto primitive, two payload domains): the signature covers EVERY field except `signature` itself — `signature_algorithm` INCLUDED, so flipping the algorithm tag without recomputing the signature fails verification (downgrade-attack defence). Verification model (be precise about the guarantee): the HMAC secret never leaves Apier, so this receipt is APIER-VERIFIABLE integrity — Apier's attestation, re-checkable by Apier at any time — NOT an independently/offline consumer-verifiable signature (that would require an asymmetric scheme; the versioned `signature_algorithm` field leaves room for such a migration). Holding the receipt still pins every signed field: any later tampering is provable the moment Apier re-verifies. The signature is safe to hold client-side (it contains no secret material). Emitted inline by POST /v1/fullmakt/request (201, event_type=delegation_granted) and POST /v1/fullmakt/revoke (200, event_type=delegation_revoked, fresh revocations only); re-fetchable via GET /v1/fullmakt/receipts, whose entries nest this exact object — the shape Apier's verifier accepts.
        - `receipt_id` string, uuid, required: Route-minted receipt identifier — INSIDE the signed HMAC domain (minted before signing, so the id itself is tamper-evident). Unique per receipt.
        - `event_type` 'delegation_granted' | 'delegation_revoked', required: Which fullmakt lifecycle event this receipt proves. `delegation_granted` — a delegation was brokered and durably recorded. `delegation_revoked` — a live delegation was durably revoked (revoke-by-insert marker). Closed set.
        - `consumer_id` string, uuid, required: The Apier consumer that held the API key which performed the event — the C in "consumer C obtained a delegation for org O".
        - `org_number` string, required: Norwegian organisation number of the CUSTOMER company the delegation applies to (Brønnøysund format, exactly 9 digits).
        - `system_user_id` string, nullable, required: The Altinn systembruker the delegation binds — the S in "under systembruker S". Nullable in the schema for forward-compatibility; both current emitters always carry the bound id.
        - `agent_principal_id` string, uuid, required: The agent principal the lifecycle event anchors to.
        - `scopes` string[], required: Scope set the delegation carried at event time — what "scoped" means in the proof. Frozen verbatim; part of the signed domain.
        - `granted_packages` string[], nullable, required: PROVISIONAL Altinn access packages the delegation row carried (intended-mapping-derived, NOT Altinn-confirmed). Null = unknown. Frozen verbatim so the receipt records what Apier believed at event time.
        - `delegation_status` 'pending' | 'active' | 'expired' | 'revoked', required: Delegation lifecycle state AT SIGNING TIME — 'pending'/'active' on a grant (pending until the signing authority approves), 'revoked' on a revocation.
        - `valid_until` string, date-time, nullable, required: Delegation expiry at event time (null = indefinite). On a delegation_revoked receipt this is the REVOCATION instant — when the authority ended. Millisecond-precision UTC (the exact string form is inside the signed domain).
        - `audit_log_id` string, uuid, required: The immutable audit_log row for the fullmakt.request / fullmakt.revoke action that produced this receipt — the receipt-to-audit forensic join.
        - `correlation_id` string, uuid, required: X-Correlation-ID of the originating request. Joins audit_log / provenance_log on the shared forensic axis.
        - `signed_at` string, date-time, required: When the receipt was signed — the T in "at time T". Millisecond-precision UTC; inside the signed domain.
        - `signature_algorithm` 'HMAC-SHA256-v1', required: Versioned algorithm tag — INSIDE the signed domain (downgrade-attack defence). A future rotation introduces a new enum value; historical receipts keep verifying under the tag they were signed with.
        - `signature` string, required: HMAC-SHA256 hex over the canonical-JSON serialisation of every other field. Verifiable ONLY by Apier (the HMAC secret never leaves the server) — treat a verified receipt as Apier's attestation, never as a third-party- or offline-consumer-verifiable signature.
    - `pagination` object, required: Keyset pagination state (limit+1 lookahead). When `has_more` is true, pass `next_before` and `next_before_id` back as `?before=` and `?before_id=` for the next page.
      - `limit` integer, required
      - `has_more` boolean, required
      - `next_before` string, date-time
      - `next_before_id` string, uuid
  - `_meta` TrustMetadata, required: Metadata included in every response for trust and verifiability.
    - `rulebook_version` string, required: Current Rulebook version. Internal rule-version records carry structured origin metadata (`initial_seed` | `human_review` | `lovdata_drift_response` | `audit_finding` | `customer_question` | `legal_correction`) for operator forensics, but that attribution is deliberately NOT exposed on public responses to avoid leaking operational signal.
    - `data_freshness` string, date-time, required: When this data was last fetched (ISO 8601 UTC).
    - `last_verified` string, date-time, required: When this data was last verified against source (ISO 8601 UTC).
    - `source` string, required: Origin of this data. Defaults to `apier.no`. The agent-readiness probe (`GET /api/v1/health/agent-readiness`) is the one surface that may instead emit `apier.no telemetry` — it does so when at least one of its endpoint rates came from measured live telemetry, and falls back to `apier.no` when every rate is a static default; all other endpoints always emit `apier.no`.
    - `data_source` string: Authoritative origin of the underlying data (listed alongside rulebook_version, data_freshness, last_verified, legal_basis for Rulebook-influenced endpoints). Distinct from `source` (the response origin): `data_source` identifies the authoritative data publisher — e.g. 'Brønnøysund Enhetsregisteret + Apier Universal Rulebook'. Present on registry-backed endpoints.
    - `served_from` 'cache' | 'live' | 'static': Cache-aware endpoints only — 'cache' when the response was served from the local copy, 'live' when the gateway just refreshed from the upstream, 'static' when the payload was computed deterministically from pure code with no DB or upstream read (e.g. /v1/public/deadlines). Absent on endpoints that don't carry this semantic.
    - `stale` boolean: Cache-aware endpoints only — true when the upstream was unreachable and a within-limit cached row was served as a fallback. Absent on normal responses.
    - `schema_version` string, required: OpenAPI contract version at the time of the response; matches `info.version`. Always present on every `/v1/*` response so a future schema break can be traced to the exact rows / audit events that predate / postdate it. Agent-facing machine interfaces (v1/capabilities, workflows.json) may override with their own narrower surface version; all other endpoints inherit the manifest-level version.
    - `legal_basis` string: Legal basis under which the response data is reused. Present on Rulebook-influenced endpoints (v1/company/{org}/obligations, /v1/company/{org}/deadlines). Common value: 'NLOD — public registry reuse'.
    - `rule_count` integer: Rule-evaluation count — total rules evaluated for this request. Present on endpoints that invoke the Rulebook evaluator (v1/company/{org}/obligations).
    - `applicable_count` integer: Count of rules whose evaluation_result is 'applicable'. Present on evaluator endpoints.
    - `not_applicable_count` integer: Count of rules whose evaluation_result is 'not_applicable'. Present on evaluator endpoints.
    - `insufficient_data_count` integer: Count of rules whose evaluation_result is 'insufficient_data' (Tier 2 gated). Present on evaluator endpoints. rule_count = applicable_count + not_applicable_count + insufficient_data_count.
    - `cache_age_ms` integer, nullable: Cache layer: milliseconds since the cached row was computed, or null on a cache miss (served_from === 'live'). Agents use it alongside data_freshness as a staleness signal. Present on endpoints wired to the cache (v1/company/{org}/obligations, /deadlines, /summary, /v1/public/obligations, /v1/public/deadlines).
    - `response_time_ms` integer: Speed signal: total server-side processing time in milliseconds, measured via performance.now() at the route boundary. Mirrored on the `X-Apier-Response-Time-Ms` header so agents can key on it without parsing the body. Present on every endpoint.
    - `response_timestamp` string, date-time: RFC 3339 / ISO 8601 UTC timestamp stamped by the response builder at wire-exit. Mirrored on the `provenance_log.response_timestamp` column by a fire-and-forget writer. Distinct from `data_freshness` (when upstream data was fetched) and `last_verified` (when the citation was verified); this is the moment the envelope left the server. Always populated at runtime — deliberately left out of the `required` list to avoid a cascading contract change that would invalidate every pre-existing example envelope in this spec (append-only response contracts). A future revision may promote it into the `required` list alongside a bulk example refresh.
    - `response_hash` string: SHA-256 hash of the canonical-JSON form of the envelope with `_meta` stripped before hashing, prefixed with `sha256:`. Mirrored on `provenance_log.response_hash` so a consumer can independently re-hash the bytes they received and compare against what we persisted (integrity receipt). Stripping `_meta` is load-bearing: volatile fields (response_time_ms, cache_age_ms, served_from) and the hash itself would otherwise feed into the digest and break the cache-hit-bytewise-identical invariant.
    - `source_snapshot_id` string: Optional free-text pointer into an upstream sync snapshot the response derives from — e.g. a Brreg sync's `brreg-<ISO>` snapshot id. Absent when the response is not tied to a specific upstream snapshot (capabilities, tools, static deadlines).
    - `is_sandbox` true: Present and `true` only when the response was generated from sandbox fixture data (currently `ALTINN_MODE=sandbox` on `/api/v1/altinn/list-acting-capacity`). Absent (NOT `false`) on every other response — the absent-vs-false distinction is deliberate so downstream agents branching on `if (response._meta.is_sandbox)` cannot be misled into treating non-sandbox responses as positively-confirmed-not-sandbox. Distinct from the `/v1/sandbox/*` `is_sandbox: true` literal in `SandboxMeta` (which carries the sandbox surface tag); this flag rides through the production `/api/v1/altinn/*` surface to forensically tag a sandbox-mode response that an OEM evaluator received.
    - `cost_nok` number: What this call debited from the caller's prepaid credit balance, in NOK, rendered from the integer-øre ledger (50 øre → 0.5; the ledger itself never leaves whole øre and no float arithmetic touches a balance). Present on the 2xx body of every metered company-data read — the same debit that sets the `X-Credits-Cost-Ore` header, so the two never disagree. `0` when nothing was charged: credit enforcement running dark (the response then also carries `X-Credit-Check: shadow`) or the sandbox surface. Absent on unmetered endpoints and on error envelopes — a refunded 5xx/403/404 claims no cost rather than a wrong one. Lives under `_meta`, which `response_hash` excludes, so the provenance receipt is unaffected; the route's ETag is computed before the credit wrapper stamps it, so a conditional request can still short-circuit to 304. Append-only addition.
    - `wallet_remaining_nok` number, nullable: The prepaid credit balance remaining AFTER this call's debit, in NOK (same rendering as `cost_nok`; mirrors the `X-Credits-Balance-Ore` header). `null` when no balance was read: credit enforcement running dark, or the sandbox surface. Present wherever `cost_nok` is. An agent planning a sequence of metered calls can divide this by the per-call price from GET /api/v1/pricing to know how many reads remain before a 402 INSUFFICIENT_CREDITS. Append-only addition.
    - `spend_cap_remaining_nok` number: What the calling key may still spend under its tighter spend cap (Europe/Oslo calendar day or month) AFTER this call's debit, in NOK (same rendering as `cost_nok`; never below 0). Present on the 2xx body of a metered read only when credit enforcement is live AND the key has a daily or monthly cap (set with PATCH /api/v1/account/keys/{id}); absent otherwise. When it reaches 0 the next metered call on this key returns 402 SPEND_CAP_REACHED until the cap resets. Append-only addition.

## Other responses

- `304`: Not Modified — the `If-None-Match` value matches the current strong ETag; the receipt list is unchanged since the response that ETag was issued for. No body.
- `400`: Invalid query parameters — limit out of range, malformed cursor values, or a half-supplied keyset tuple (`before` without `before_id` or vice versa). error_code=VALIDATION_FAILED.
- `401`: Authentication failed — missing, malformed, invalid, or revoked API key.
- `403`: The API key lacks the read:altinn scope (error_code=SCOPE_INSUFFICIENT) — the same ACTIVE per-data-source scope every fullmakt sibling requires.
- `429`: Rate limit reached on at least one of TWO independent dimensions running in parallel: per-(api_key, endpoint) per-minute (the established per-tier scaling — Free / Starter / Professional / Enterprise unlimited) AND per-(api_key, org_number) per-day (bounds runaway-agent failure modes per client org so one org's traffic cannot starve siblings sharing the same key; daily bucket window is one calendar day in Europe/Oslo, DST-aware). The `X-RateLimit-Dimension` header identifies which bucket tripped: `per_key`, `per_org`, or `both` (when the same request exceeds both — the binding Retry-After is the per-org value because the per-org window is hours/days vs the per-minute window). The `Retry-After` header indicates how many seconds to wait before the binding window resets; `X-RateLimit-Limit` / `X-RateLimit-Remaining` / `X-RateLimit-Reset` describe the per-minute bucket state. The per-day per-org limits per tier (sized at ~100× typical daily volume — the dimension exists to bound failure modes, not to monetize) are: Free 1000/org/day, Starter 5000, Professional 25000, Enterprise unlimited. On rare infrastructure-side failures the gateway fails OPEN and passes the request through with `X-RateLimit-Check: skipped` on the response — clients can treat that as a transient signal that quota enforcement was briefly degraded.
- `500`: Unexpected failure reading the receipts (typically a database read failure or a row that no longer matches the expected receipt shape). Nothing about the request was wrong — retry later. error_code=SERVER_ERROR.

---

[API](https://skmtc.dev/apier/apis/apier-no-api.md) · [All operations](https://skmtc.dev/apier/apis/apier-no-api/llms.txt) · [OpenAPI document](https://skmtc.dev/apier/apis/apier-no-api/revisions/9ec19bc87311?raw)