Changes to the API
The provider API is version 1, at https://gw.kairosinnovations.dev/api/v1/ingest/telemetry. This page explains how it changes and how to keep your client working when it does.
4 November 2026: One provider per plate
IFMS now accepts positions for a plate from one provider only. The first provider whose position for the plate is accepted holds it. Positions from other providers are refused with the new failure reason PLATE_HELD_BY_ANOTHER_PROVIDER, and the refusal's message names the holding provider. The hold ends when IFTMS records a change of operator or removal, or after 30 days without positions from the holder. See One provider per plate. The address, version, payload and the other failure reasons are unchanged.
16 October 2026: Provider API renamed
At the request of the Ministry of Transport and Logistics, the API was renamed to IFMS FMS Service Provider Integration API in the Developer Portal. The address (https://gw.kairosinnovations.dev/api/v1/ingest/telemetry), version 1.0.0, keys, tokens and payload are unchanged. The IFMS team moved every subscribed application to the renamed API the same day. If your application was subscribed before, it still is, and you do not need to do anything.
Controlled changes
IFMS treats these as controlled interface changes, and communicates them before they are enforced:
- the required fields;
- validation ranges;
- authentication;
- what a response means;
- the failure reasons;
- the endpoint path.
Additive changes
Some changes are additive: they add something without breaking what is already there. Build your client so that it keeps working when they arrive.
- New failure reasons. The set of failure
reasoncodes is explicitly additive. Treatreasonandoutcomevalues as plain strings. When you see a value you do not recognise, log it as it is instead of failing. - New response fields. Ignore fields in the response that you do not recognise.
- Request fields. Send only the fields in the contract. IFMS ignores fields it does not recognise, so never rely on one being processed. A provider-specific value does not become a contract field without a formal review.
Use the unversioned address
Post to https://gw.kairosinnovations.dev/api/v1/ingest/telemetry, not to the versioned address some Developer Portal screens show. Send your first batch explains why.
Where to see what changed
- The Changelog lists the changes published to the provider API contract.
- The provider API reference shows the current contract.
- Sending telemetry describes the fields, limits and failure reasons in full.