---
title: "Public sandbox mirror of /api/v1/company/{org}/context (zero-auth, IP rate-limited)"
method: GET
path: "/api/v1/sandbox/public/company/{org}/context"
tags: ["Sandbox"]
---

# Public sandbox mirror of /api/v1/company/{org}/context (zero-auth, IP rate-limited)

`GET /api/v1/sandbox/public/company/{org}/context`

## Request

- Base URL: `https://www.apier.no`
- URL: `https://www.apier.no/api/v1/sandbox/public/company/{org}/context`
- Auth: none required

Unauthenticated. Per-IP rate limit 100 requests / hour on the dedicated 'public-sandbox' bucket. Org 999999999 only. Response shape is byte-equivalent to the internal `/api/v1/sandbox/company/{org}/context` mirror (reuses the same SandboxContextEnvelope schema). Two header differences from the internal surface: `Access-Control-Allow-Methods: GET, POST, OPTIONS` (unified across the public-sandbox routes); `X-Robots-Tag: noindex` and `X-Apier-Sandbox: public` are added so SDK clients can detect the surface without parsing the URL. PROVENANCE EXEMPT — no `_meta.response_hash`, no `provenance_log` row (sandbox carve-out). Unknown query parameters return 400 VALIDATION_FAILED (the only accepted keys are `simulate_error` and the parameters documented on this operation). A 200 carries X-RateLimit-Limit / -Remaining / -Reset for the per-IP clock-hour bucket; a 429 states the same 100-per-clock-hour limit, resetting at the top of the hour.

## Query parameters

- `simulate_error` 'missing_delegation' | 'invalid_token' | 'validation_error' | 'scope_missing' | 'altinn_timeout' | 'invalid_certificate' | 'malformed_payload' | 'upstream_5xx' | 'AUTH_MISSING_DELEGATION' | 'AUTH_EXPIRED_TOKEN' | 'VALIDATION_FAILED' | 'SCOPE_MISSING'

## Response `200`

Public-sandbox 2xx success for `GET /api/v1/sandbox/public/company/{org}/context`. Same `SandboxContextEnvelope` body schema as the internal `SandboxContextSuccess` (`{ success: true, data: SandboxContextData, _meta: SandboxMeta }`). The example body is the public fixture (org `999999999`, `Apier Public Sandbox AS`) as the public mirror serves it; the internal component's example uses the 999000001-005 pool, which this surface rejects with 400 PUBLIC_SANDBOX_ORG_NOT_PERMITTED. Two header differences from the internal mirror: `Access-Control-Allow-Methods: GET, POST, OPTIONS` (unified across the public-sandbox routes), and the added `X-Robots-Tag: noindex` + `X-Apier-Sandbox: public` detection markers. `Access-Control-Allow-Credentials` is INTENTIONALLY absent — the public sandbox is zero-auth.

- SandboxContextEnvelope: Sandbox 2xx success envelope BASE shape. Top-level keys mirror the production envelope (`success`, `_meta`) so SDK clients consuming sandbox responses see identical shapes. The `data` field is intentionally omitted from the base — per-operation envelopes (`SandboxContextEnvelope`, `SandboxObligationsEnvelope`, ...) `allOf` this base and pin `data` to the operation's typed payload, so generated clients keep the mirror typing for each route.
  - `success` true, required
  - `_meta` SandboxMeta, required: Sandbox `_meta` block. NOT a drop-in for production's `TrustMetadata`; clients must branch on `is_sandbox` before assuming any sandbox/production field equivalence. Differences from production: 1. `is_sandbox: true` — load-bearing detection signal; `body._meta.is_sandbox === true` is a single property assertion agents use to verify they're talking to the sandbox. Production omits this key entirely. 2. `rulebook_version` is the literal string `"sandbox"` — production carries the actual Rulebook version (e.g. `"v1.0.0"`). Sandbox responses are not Rulebook-evaluated. 3. `data_freshness` and `last_verified` are pinned constants (2026-01-01T00:00:00+01:00) — production reflects actual cache / fetch state. 4. `response_timestamp` is RFC 3339 with explicit Europe/Oslo offset (`+01:00` CET / `+02:00` CEST, DST-aware) — production's `response_timestamp` carries a UTC `Z` suffix. 5. `response_hash` and `source_snapshot_id` are OMITTED — sandbox writes ZERO provenance_log rows, so a hash without a matching forensic row would be misleading. Only `source` (`"apier.no"`) and `schema_version` semantics are shared with production.
    - `rulebook_version` 'sandbox', required: Always literal `sandbox` — sandbox responses are not Rulebook-evaluated.
    - `data_freshness` '2026-01-01T00:00:00+01:00', date-time, required: Pinned constant (2026-01-01T00:00:00+01:00) for determinism — same value on every call. Schema-locked via `enum` so spec-based drift checks catch any deviation.
    - `last_verified` '2026-01-01T00:00:00+01:00', date-time, required: Pinned constant — equal to data_freshness. Schema-locked via `enum` for the same drift-detection reason.
    - `source` 'apier.no', required: Response origin. Always `apier.no`. Preserves `_meta.source` parity with production `TrustMetadata.source` so clients can reuse `_meta` parsing across both surfaces. Provenance-specific fields (`response_hash`, `source_snapshot_id`) are omitted by design.
    - `schema_version` string, required: OpenAPI document version — mirrors the top-level `info.version` field. Distinct from `/api/v1/capabilities._meta.schema_version` and `/workflows.json.schema_version`, which version the capabilities-discovery and workflows-discovery surfaces respectively. Equality with `info.version` is enforced at CI time.
    - `is_sandbox` true, required: Load-bearing sandbox-detection signal. Always `true`.
    - `response_timestamp` string, date-time, required: RFC 3339 timestamp with explicit Europe/Oslo offset — runtime emits via `formatInTimeZone(now, 'Europe/Oslo', "yyyy-MM-dd'T'HH:mm:ssXXX")` so the offset is DST-aware (`+01:00` in CET / `+02:00` in CEST). The ONLY non-deterministic field permitted on sandbox responses (excluded from determinism comparisons).
    - `sandbox_notice` string, required: Human-readable mock-vs-government honesty signal (item 5). Constant prose: a passing sandbox run is an Apier internal mock (not Altinn TT02 / Skatteetaten test) and does not guarantee real government acceptance. `is_sandbox` is the machine-readable twin; this is the prose an agent or a human reading a logged response sees. Plain ASCII so it never trips the docs bokmål canary.
    - `cost_nok` 0: Always `0`. A sandbox call never debits anything — there is no ledger write and no government upstream. Same field name and rendering as production's `TrustMetadata.cost_nok`, so a client that reads the cost off `_meta` works unchanged against both surfaces. Emitted on every sandbox response. Declared optional in this schema only so the many older sandbox examples in this document stay valid; the runtime builder emits it on every response.
    - `wallet_remaining_nok` unknown
    - `as_of` string: Present ONLY when `?as_of=` Rulebook time travel is active on /deadlines or /obligations. Echoes the agent's exact YYYY-MM-DD input so a transcript is self-describing about which reference date the deadline / obligation statuses were derived against. Absent on every other sandbox response.
    - `simulated` true: Present + `true` ONLY on an `X-Apier-Simulate` injected failure response. The load-bearing signal that a 500 / 504 / 429 is a deliberately-simulated infrastructure failure, not a real one. Absent on every real sandbox response.
    - `session_merged` true: Present + `true` ONLY when this response merged per-suffix session state (mock filings recorded by a prior POST /api/v1/sandbox/actions/execute under the SAME sandbox-bearer suffix) over the static fixture, on the three opted-in reads (/audit, /obligations, /summary). The honesty marker distinguishing fixture state from session state. Absent on every fresh-suffix response, which stays byte-deterministic.
    - `session_merged_rows` integer: Count of response items the merged session state changed (obligation/deadline statuses overridden plus audit rows prepended). Present ONLY alongside `session_merged: true`, always >= 1.
  - `data` SandboxContextData, required: Top-level data shape returned by GET /api/v1/sandbox/company/{org}/context. Standalone sandbox-specific shape — NOT a drop-in for the production `CompanyContext` schema. Documented divergences: `status` is uppercase enum (`ACTIVE`/`INACTIVE`) where production carries lowercase free text; `data_tier` includes `tier_1_2` for the Tier 1+2 fixture where production exposes the binary `[tier_1, tier_2]` enum; `registration_date` is bare `YYYY-MM-DD` where production carries an ISO 8601 datetime; the `aareg` block carries an additional `note` field that production's `additionalProperties: false` would reject. Sandbox `_meta` is `SandboxMeta` (not `TrustMetadata`). All values are deeply frozen at module load.
    - `org_number` string, required
    - `name` string, required
    - `entity_type` 'AS' | 'ENK', required
    - `nace_codes` string[], required
    - `status` 'ACTIVE' | 'INACTIVE', required
    - `municipality` string, required
    - `registration_date` string, date, required
    - `signaturrett` object[], required
      - `role` string, required
      - `name` string, required
    - `prokura` object[], required
      - `role` string, required
      - `name` string, required
    - `data_tier` 'tier_1' | 'tier_1_2', required
    - `tier_2` object, nullable, required
      - `employee_count` integer, nullable, required
      - `annual_turnover` number, nullable, required
      - `total_assets` number, nullable, required
      - `mva_registered` boolean, nullable, required
      - `mva_registration_date` string, date, nullable, required
    - `tier_2_note` string, nullable, required
    - `upgrade_path` string, nullable, required
    - `aareg` object, required
      - `available` false, required
      - `reason` 'DELEGATION_MISSING_NAV_AAREG', required
      - `note` string, required
    - `skatteetaten` object, required: Skatteetaten Tier-2 sub-results. The two delegation-gated sub-results (`mva_meldinger`, `skatteoppgjor`) mirror production's `SkatteetatenSubResultUnavailable` shape: when `reason` is `DELEGATION_MISSING` (or `SCOPE_NOT_YET_APPROVED`), the `scope` field carries the Maskinporten scope string the consumer needs to delegate. Sandbox always emits the unavailable branch with `DELEGATION_MISSING` + the canonical scope. `mva_register` is permanently null (retired sub-client) to mirror the production contract.
      - `mva_register` unknown, required
      - `mva_meldinger` object, required
        - `available` false, required
        - `reason` 'DELEGATION_MISSING', required
        - `scope` 'skatteetaten:mva-melding-list-read', required
      - `skatteoppgjor` object, required
        - `available` false, required
        - `reason` 'DELEGATION_MISSING', required
        - `scope` 'skatteetaten:skatteoppgjor-read', required
    - `konkurs` boolean, nullable, required: Production field: the company is in bankruptcy. Read from the fixture.
    - `under_avvikling` boolean, nullable, required: Production field: the company is being wound up. Read from the fixture.
    - `under_tvangsavvikling` boolean, nullable, required: Production field: the company is being forcibly dissolved. Read from the fixture.
    - `mva_registered` boolean, nullable, required: Production field: the company is in the VAT register. Read from the fixture.
    - `has_filed_annual_accounts` boolean, nullable, required: Production field: the company has filed annual accounts. Read from the fixture.
    - `last_accounts_year` integer, nullable, required: Production field: the latest financial year with filed annual accounts. Read from the fixture.

## Other responses

- `400`: 4xx / 5xx error from a public-sandbox route (`/api/v1/sandbox/public/*`). Body shape uses the public-surface error_code vocabulary defined in `PublicSandboxEnvelopeError` (adds `PUBLIC_SANDBOX_ORG_NOT_PERMITTED`, `PUBLIC_SANDBOX_BODY_TOO_LARGE`, `RATE_LIMIT_EXCEEDED` on top of the internal sandbox set). Response carries the public-sandbox-specific header set: `Access-Control-Allow-Methods: GET, POST, OPTIONS`, `X-Robots-Tag: noindex`, `X-Apier-Sandbox: public`. `Access-Control-Allow-Credentials` is INTENTIONALLY absent. On 429 responses, `Retry-After` carries the seconds-until-bucket-reset for the per-IP rate-limit window.
- `429`: 4xx / 5xx error from a public-sandbox route (`/api/v1/sandbox/public/*`). Body shape uses the public-surface error_code vocabulary defined in `PublicSandboxEnvelopeError` (adds `PUBLIC_SANDBOX_ORG_NOT_PERMITTED`, `PUBLIC_SANDBOX_BODY_TOO_LARGE`, `RATE_LIMIT_EXCEEDED` on top of the internal sandbox set). Response carries the public-sandbox-specific header set: `Access-Control-Allow-Methods: GET, POST, OPTIONS`, `X-Robots-Tag: noindex`, `X-Apier-Sandbox: public`. `Access-Control-Allow-Credentials` is INTENTIONALLY absent. On 429 responses, `Retry-After` carries the seconds-until-bucket-reset for the per-IP rate-limit window.
- `500`: 4xx / 5xx error from a public-sandbox route (`/api/v1/sandbox/public/*`). Body shape uses the public-surface error_code vocabulary defined in `PublicSandboxEnvelopeError` (adds `PUBLIC_SANDBOX_ORG_NOT_PERMITTED`, `PUBLIC_SANDBOX_BODY_TOO_LARGE`, `RATE_LIMIT_EXCEEDED` on top of the internal sandbox set). Response carries the public-sandbox-specific header set: `Access-Control-Allow-Methods: GET, POST, OPTIONS`, `X-Robots-Tag: noindex`, `X-Apier-Sandbox: public`. `Access-Control-Allow-Credentials` is INTENTIONALLY absent. On 429 responses, `Retry-After` carries the seconds-until-bucket-reset for the per-IP rate-limit window.

---

[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)