Data & API

Consuming AiR data

Illustrative endpoints for sessions, vehicles, fleet compliance and aggregated network insight.

Simulated real-world data being used for demonstration purposes

GET /v1/sessions/:id

Full session record: targets, per-channel corrections, alerts and outcome.

GET /v1/vehicles/:reg/history

Session history and repeat-loss detection for a saved vehicle.

GET /v1/fleets/:id/compliance

Fleet compliance summary, exceptions and overdue vehicles.

GET /v1/network/regions

Aggregated regional deviation, correction and leak-rate metrics.

POST /v1/machines/:id/telemetry

Machine health, channel cycles, calibration and connectivity.

Illustrative interface design. No endpoints are live in this demonstration.

Evidence base

What makes this data worth consuming

The value of a session record is that every field is defined against an external standard, so records are comparable across vehicles, sites and years.

Deviation is defined, not inferred

Each channel carries the approved target it was measured against, taken from a published load table.2025

Temperature context travels with the reading

Because pressure is temperature-dependent, a record without temperature is not comparable. Both are stored.2006,2018

Thresholds map to regulation

Severity bands align with the type-approval warning threshold and with the pressure-error levels used in crash analysis.2016,2012

Aggregates match official series

Regional and temporal aggregation is designed to be joinable to published casualty and MOT statistics.2025,2026

These are published third-party sources, not AiR simulation. The full bibliography - peer-reviewed papers, reference monographs, government reports, international standards and official statistics - lives in the science lab.

Open the research and full bibliography
/Session records/Vehicle profiles/Fleet exports/Network aggregates/Webhooks/Versioned schemas/Session records/Vehicle profiles/Fleet exports/Network aggregates/Webhooks/Versioned schemas

Integration

Data that other systems can actually consume

A session record is only useful if it reaches the fleet platform, the leasing system or the safety dataset without a spreadsheet in the middle.

Core resources

0

Delivery modes

0

REST pull, webhook push, scheduled export.

Schema versioning

0%

Every payload carries a version and an immutable session id.

Personal data in aggregates

0

Sessions, vehicles, sites, fleets and aggregates. Session records are immutable once closed; corrections are issued as new records referencing the original.

  • Session: per-channel before, target, after, tolerance and status
  • Vehicle: class, fitment and approved profile version used
  • Site: unit identity, uptime and throughput
  • Fleet: compliance, exceptions and history within a tenancy
  • Aggregate: anonymised regional and class-level condition data

Questions

Straight answers

No. The API exposes what was recommended and what was measured, not the licensed manufacturer tables behind it.