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
Cited on this page
- European Tyre and Rim Technical Organisation (2025). ETRTO Standards Manual - load capacity and inflation pressure tables. ETRTO, Brussels, annual edition.
- International Organization for Standardization (2018). ISO 28580: Passenger car, truck and bus tyre rolling resistance measurement method. ISO.
- United Nations Economic Commission for Europe (2016). UN Regulation No. 64 - Temporary-use spare units, run-flat tyres and tyre pressure monitoring systems. UNECE World Forum for Harmonization of Vehicle Regulations.
- UK Department for Transport (2025). Reported road casualties in Great Britain (annual statistics). DfT official statistics.
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 bibliographyIntegration
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
