Developer Preview

Executable Example

Consume the API through the Five Acts of Insurance.

Start with a tenant-neutral read journey derived from the canonical Five Acts demo: parties/roles, covers/products, policies/versions, premiums/payments, and events/assertions without inventing unavailable fields.

Why This Example Exists

The Five Acts model gives builders one insurance story that touches parties/roles, covers/products, policies/versions, premiums/payments, and events/assertions. This public version is sanitized for developer-preview use while staying synchronized with the canonical demo facts.

Run The Python SDK Example

Dry-run mode validates the scenario and prints the SDK call sequence. Live mode requires a backend-held bearer token and a server-minted tenant-context token from an issued alpha access pack. 

PYTHONPATH=packages/axiom-python/src \
python3 app/frontdoors/sites/developers/api/examples/five-acts/python/five_acts_read_journey.py \
  --dry-run \
  --scenario app/frontdoors/sites/developers/api/examples/five-acts/scenario.json
export AXIOM_ACCESS_TOKEN=<jwt>
export AXIOM_TENANT_CONTEXT=<server-minted tenant context>
PYTHONPATH=packages/axiom-python/src \
python3 app/frontdoors/sites/developers/api/examples/five-acts/python/five_acts_read_journey.py

Journey Map

Act Developer task API operations
Parties and roles List admitted parties and inspect selected party context. GET /v1/parties, GET /v1/parties/{id}
Products and covers Treat product and cover setup as tenant configuration. GET /v1/catalogues, GET /v1/catalogues/{catalogue-ref}/entries
Policies and terms List policies and open selected policy detail. GET /v1/policies, GET /v1/policies/{id}
Premiums and payments Display premium and payment context where the contract exposes it. GET /v1/premiums, GET /v1/payments
Events and assertions Read retained claim-family compatibility data as events/assertions. GET /v1/claims, GET /v1/claims/{id}, GET /v1/claims/{id}/pdf

Rules For Using It

  • Keep bearer tokens and tenant-context tokens on your backend.
  • Use only tenant context minted by Axiom for your admitted account.
  • Do not add fields to screen code just because the demo story mentions them.
  • Record unavailable behaviour as an explicit application gap.

Freshness Guard

The public scenario JSON is generated from the canonical Five Acts demo story and records the source revision and SHA-256. The developer checks fail when the generated scenario or rights sidecar drifts from that source. 

npm run developer:examples:check

A nightly synchronization check runs the same freshness proof. When an admitted canary access pack is configured, that nightly path also runs the live read journey through the public API. Until then, live canary status is explicitly reported as not configured rather than implied.