Integrate with contracts, states and evidence
Start from the workflow, read OpenAPI, validate schemas and rehearse failures before requesting a sandbox.
Choose a starting point
Integration quickstart
Exercise ingest → job tracking → registration → verification with synthetic data.
Read detailsOpenAPI and Swagger Reference
The proposed contract is rendered from one local specification; no network Try-It or real credentials.
Read detailsEnd-to-end integration workflows
Connect technical states to business decisions instead of merely listing endpoints.
Read detailsAPI Explorer — local simulator
Explore requests/responses and failure scenarios using synthetic data; no backend connection.
Read detailsDevice/Edge integration
Device command contracts retain commandId, SheetID, deadlines, acknowledgements and recovery semantics.
Read detailsNAPAS QR and Trusted Billing
Integration design separates payment confirmation, reconciliation and invoice issuance.
Read detailsAPI catalog by domain
| Domain | HTTP | Operation / path | Scope | Synthetic result |
|---|---|---|---|---|
| Intake | POST | Ingest packages/v1/ingest-packages | ingest:write | 202 |
| Records | POST | Registration and declaration/v1/records/declarations | records:declare | 202 |
| Records | PATCH | Controlled metadata updates/v1/records/{recordId}/metadata | records:metadata | 202 |
| Jobs | GET | Processing jobs and status/v1/jobs/{jobId} | jobs:read | 200 |
| Access | POST | Record search/v1/records/search | records:read | 200 |
| Access | POST | Access requests/v1/access-requests | access:request | 202 |
| Preservation | POST | Preservation packages/v1/preservation-packages | preservation:write | 202 |
| Acceptance | POST | Delivery and acceptance/v1/deliveries/{deliveryId}/acceptance | delivery:accept | 202 |
| Evidence | POST | Evidence verification/v1/evidence/verification | evidence:verify | 200 |
| Device/Edge | POST | Flow R routing decision/v1/device-commands | devices:command | 202 |
| Billing | POST | Payment request/v1/payment-requests | billing:write | 202 |
| Billing | GET | Payment status/v1/payment-requests/{paymentRequestId} | billing:read | 200 |
| Billing | POST | Invoice request/v1/invoice-requests | billing:write | 202 |
| Billing | GET | Invoice status/v1/invoice-requests/{invoiceRequestId} | billing:read | 200 |
Learn by task, inspect the contract
Service Playground — task-based experience
Exercise a records workflow with forms, requests/responses and a timeline. Use synthetic data in offline simulation or a local HTTP mock.
Read detailsLTANS and evidence-preservation integration
The Records–provider boundary covers validation, profiles, receipts, status and export. Website contracts are design proposals, not Mobile-ID LTANS APIs.
Read detailsPreservation Profile Center
Choose preservation configurations by record class, designated community and required evidence. Illustrative profiles are not approved service offerings.
Read detailsSample package export and verification
Check synthetic-package hashes before delivery; distinguish byte integrity from authenticity, signatures and legal status.
Read detailsFinal sources tied to business decisions
Three environments, three evaluation methods
Reference: delivered design contracts, not released. Simulation: browser-local Explorer with synthetic data and no network calls. Sandbox: exercise only Mobile-ID-issued endpoints, credentials, scopes and permitted data. The offline package contains no backend or production environment.
Integration results require verification
HTTP 202 accepts a request rather than declaring a record; command ACK does not prove paper arrival; payment confirmed does not mean invoice issued. Track identifiers/correlation, terminal states, manifest/version and reconciliation evidence.
Continue the workflow
Two journeys, one records lifecycle
Connect paper and born-digital records through persistent identifiers, policies and evidence.
Read detailsIntegration quickstart
Exercise ingest → job tracking → registration → verification with synthetic data.
Read detailsIntegrity, provenance and evidence
Each evidence type answers a different question; hashes, timestamps and approvals are not interchangeable.
Read detailsStart with a verifiable scope.
Agree record classes, quality criteria, permissions and evidence before scaling.
Plan assessment