Private technical preview / integration kit

The contract,
before the credentials.

Inspect the proposed station, evidence and event model locally. Every artefact on this page is non-production and may change before customer access is offered.

Download OpenAPI Explore the API model

OPENAPI / 3.1station.latestobservation + evidence

JSON SCHEMArepresentations[]raw_tac · sha256

JSON SCHEMAintegritystate · provenance

DesignationNON-PRODUCTION PREVIEW

01 / CONTRACT FILES

Downloadable by design.

These files let a prospective pilot partner test naming, payload shape and evidence requirements without treating the preview as a released service.

OPENAPI 3.1 / YAML

Proposed HTTP surface

Planned station, observation, event and webhook-endpoint resources with example responses and explicit preview boundaries.

openapi-preview.yaml↓

JSON SCHEMA / 2020-12

Station event

A proposed event object for integrity changes, report conditions and station-level evidence references.

station-event.schema.json↓

JSON SCHEMA / 2020-12

Webhook envelope

A delivery wrapper covering event identity, signing metadata and an embedded station event.

webhook.schema.json↓

02 / REALISTIC EXAMPLES

Useful failure states included.

The examples focus on the situations the product is intended to make inspectable: exact current evidence, revision chains and a lagging distribution path.

200 / LATEST

Complete observation

Normalized station state with three representations, explicit clocks and SHA-256 content identity.

latest-observation.json ↓

200 / REVISIONS

Correction chain

An original METAR followed by a COR-qualified revision without silently replacing the earlier representation.

correction-chain.json ↓

EVENT / SOURCE LAG

Lag condition

A current-snapshot classification showing one source path on an older nominal observation time.

source-lag-event.json ↓

03 / INTEGRATION PROPOSALS

Stable ideas. Unfixed limits.

The preview makes design intent visible while leaving commercial limits, retention and production service levels open until upstream licences and pilot requirements are known.

VERSIONING

Path-major contract

Breaking changes are intended to require a new major path. Additive fields may appear within a preview version and will be recorded in the changelog.

WEBHOOK IDENTITY

Idempotent delivery

Each proposed delivery carries a stable delivery ID and event ID so receivers can discard duplicates without discarding a distinct revision.

SIGNING

HMAC proposal

The draft envelope identifies an HMAC-SHA256 key. Final header names, rotation and replay windows remain subject to pilot review.

RETRIES

Backoff, not certainty

The current proposal retries transient failures with bounded exponential backoff. No delivery guarantee or retry schedule is offered at this stage.

Technical evaluation

Test the model against a real pipeline.

We are inviting a small number of organisations to discuss scoped, non-safety-critical pilot evaluations.

Request pilot access