The FIA Driver Safety Index (DSI) is a global benchmark for driver safety that is universally accessible, complementing and enhancing existing road safety efforts for organisations worldwide.
\nBy offering a universal scoring system, the FIA DSI makes driver risk measurable, comparable and actionable – regardless of geography, industry, or vehicle type.
\nThe FIA DSI is used at a management and organisational level to measure driver risk, compare safety performance and identify areas for improvement.
\nRead more at: https://fiadsi.com/
\n","schema":"https://schema.getpostman.com/json/collection/v2.0.0/collection.json","toc":[],"owner":"18998736","collectionId":"1b6039b2-2f33-4234-80d5-69560759cfab","publishedId":"2sBXVkAoou","public":true,"customColor":{"top-bar":"fff","right-sidebar":"303030","highlight":"006ee8"},"publishDate":"2026-02-03T13:42:28.000Z"},"item":[{"name":"Getting started","item":[],"id":"967f181e-f326-4e1e-b3b0-94794fe3da3f","description":"To get started with the FIA DSI, your organisation is onboarded to a dedicated FIA DSI environment. During onboarding you will:
\nCreate your organisation FIA DSI environment
This includes setting up your company, divisions, vehicle groups and other structural entities used for analysis and benchmarking.
Configure access and credentials
API credentials are issued to allow secure access to the FIA DSI API for data ingestion and integration.
Define data scope and benchmarks
Together, we define which data sources, vehicle types and geographies should be included, and how your organisation will be benchmarked internally and externally.
Once this is complete, you can start ingesting data and using the FIA DSI for reporting, analysis and benchmarking.
\n","_postman_id":"967f181e-f326-4e1e-b3b0-94794fe3da3f"},{"name":"Ingesting data into the FIA DSI","item":[{"name":"Ingest data via API","item":[{"name":"Enumerations and classification standards","item":[],"id":"d4f88164-03be-4eb0-a01c-bc4244f3666a","description":"To ensure consistency across analytics and benchmarks, several fields use predefined values or external standards.
\nFor fields named fuelType, the following integer values are supported:
For fields named vehicleType, the following integer values are supported:
For fields named deliveryType, the following integer values are supported:
For fields named industry, values should be specified using the
Global Industry Classification Standard (GICS).
GICS is a globally recognised industry taxonomy maintained by MSCI and S&P Global, widely used for benchmarking, reporting and risk analysis.
\nExample: 20304040 → Passenger Ground Transportation
The classification is hierarchical, meaning higher-level codes are also valid
(e.g. 2030 for Transportation).
The official GICS classification and code lists can be downloaded from:
https://www.msci.com/indexes/index-resources/gics
The identifiers and classifications you provide during ingestion directly determine:
\nhow your organisation is structured in the FIA DSI,
\nhow data is aggregated,
\nhow benchmarks are computed,
\nand how insights can be queried and compared.
\nUsing consistent identifiers and classifications is therefore critical for high-quality analytics.
\n","_postman_id":"d4f88164-03be-4eb0-a01c-bc4244f3666a"},{"name":"Trip data","id":"b3508fb9-818e-45e7-9987-cd633ea79099","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"ApiKey","value":"","description":"API-key used for authorization.
\n","type":"text"},{"key":"Test","value":"0","description":"1: Test data, 0: Production data (optional)
\n","type":"text"}],"body":{"mode":"raw","raw":"{\n \"nodeId\": \"All examples below are shown in JSON format.
\nOther ingestion formats, including CSV and Protobuf, are supported.
Please contact us for details.
* At least one of vehicleId or driverId must be provided.
** Either tripId or both startTime and endTime must be provided.
For best analytical quality:
\nSamples should be provided at 1 Hz (one sample per second).
\nThe maximum supported interval between samples is 5 seconds.
\nSamples must be chronologically ordered.
\nVehicle metadata is used to enrich analytics and benchmarking.
\nUpdating vehicle fields over time will not affect historical trips, but may affect how data is grouped and compared going forward.
\nAll vehicle-related identifiers should be treated as stable over time.
\nThe FIA DSI API provides a unified way to ingest trip data and retrieve driving insights across your entire organisation.
\nWhen you send trip data to the FIA DSI, you are not only uploading individual trips — you are building the organisational structure that the FIA DSI uses for all analytics, benchmarking and risk metrics.
\nAt the core of this structure are fleets (divisions), drivers and vehicles, organised in a hierarchy defined by the identifiers you provide.
\nEach trip you upload is associated with a fleet or division node, defined by the nodeId field.
A fleet/division node is created automatically if it does not already exist.
\nThe nodeId is typically a slash-delimited path, for example:
country/company/divisionId
This hierarchy becomes the foundation for all aggregated analytics and benchmarking.
\nnodeId as a reference to your internal structureThe nodeId you provide should be treated as a stable reference to your own internal organisational identifier.
Example
\nIf your internal system uses DIV-042 as the identifier for a division, that same value should be used as nodeId when ingesting data into the FIA DSI.
If the division is later renamed, the nodeId remains the same — only the display name changes.
The FIA DSI uses metric units for all numerical values unless otherwise specified.
\nIn particular:
\nSpeed values are expected in kilometres per hour (km/h).
\nDistances are expected in metres.
\nAltitude is expected in metres.
\nProviding data in consistent metric units is required to ensure correct analysis and benchmarking.
\nDrivers and vehicles are created or updated automatically based on the identifiers you send:
\ndriverId → uniquely identifies a driver
vehicleId → uniquely identifies a vehicle
Note that this is not mandatory. Anonymous IDs can be used.
\nNo separate setup is required. As long as consistent identifiers are used, the FIA DSI will maintain and update the entities over time.
\nTrips are uploaded using either:
\n/v1/trip-data (single trip), or
/v1/trip-data/batch (multiple trips per request)
When you upload trips via these endpoints:
\nThe fleet/division hierarchy is resolved from nodeId
Drivers and vehicles are linked (or created) using driverId and vehicleId
Trip data is stored and becomes available for analytics
\nThe resulting structure can later be queried and viewed using the FIA DSI platform:
\nThis allows you to retrieve aggregated insights, safety metrics and benchmarking data at any level of the organisation.
\nOnce data is ingested, the FIA DSI automatically computes driving risk metrics and crash probability insights across fleets, drivers, vehicles and time periods.
\nThese insights are designed for organisational analysis and benchmarking, enabling comparisons across:
\ncountries and regions,
\ncities,
\nindustries,
\ninternal divisions,
\nvehicle types and usage patterns.
\nIn addition to ingesting data via the FIA DSI API, the FIA DSI can integrate directly with supported Telematics Service Providers (TSPs).
\nTSP integrations allow the FIA DSI to retrieve vehicle and trip data directly from the source system, removing the need for customers to build and maintain their own ingestion pipelines.
\nThis approach is particularly well suited for organisations that:
\nalready use a supported telematics platform,
\nwant to minimise integration effort,
\nprefer a standardised and maintained data connector.
\nFrom an analytical perspective, data ingested via TSP integrations is treated the same way as data sent through the API and becomes part of the same organisational hierarchy, benchmarks and insights.
\nTelematics integrations are available through a coordinated onboarding process. Contact us for more details.
\n","_postman_id":"0d9a5ab2-a0dd-4663-986f-f06d28cad2b2"},{"name":"Best practices and guidelines","item":[],"id":"68f17597-a868-4ccc-9bcf-09b7e3917d29","description":"The FIA DSI API is designed for long-term, large-scale analytics. Following these guidelines will help ensure stable structures and reliable benchmarks.
\nTreat nodeId, driverId and vehicleId as stable identifiers.
Do not reuse identifiers for different entities.
\nAvoid encoding meaning (such as location or role) into IDs.
\nThe display name of a node can be changed at any time without affecting:
\nhistorical data,
\nanalytics and benchmarks,
\nor existing integrations.
\nYou do not need to create a new nodeId if a division is renamed, rebranded or reorganised from a naming perspective. Changing identifiers retroactively may fragment analytics and historical comparisons.
nodeId)Keep the hierarchy consistent over time.
\nAvoid frequent restructuring of historical nodes.
\nUse meaningful but stable paths, for example:
country/company/division
The hierarchy you define directly impacts aggregation, benchmarking and trend analysis.
\nUse consistent time formats and timezones across all data sources.
\nEnsure that samples within a trip are chronologically ordered.
\nFor best analytical quality, sample data at 1 Hz (one sample per second).
\nLarge gaps between samples may reduce analytical accuracy.
\nThe FIA DSI supports flexible data delivery schedules depending on your integration and operational needs.
\nYou can choose to:
\nsend data after each completed trip, or
\nsend data as batches, for example once per day.
\nFor most organisations, daily batch delivery is recommended, as it provides a good balance between data freshness, system load and operational simplicity.
\nLess frequent deliveries are also supported, but may delay availability of insights and benchmarks.
\nA typical integration flow looks like this:
\nTrip data is uploaded via /v1/trip-data or /v1/trip-data/batch
Fleet/division hierarchy is resolved from nodeId
Drivers and vehicles are created or updated using driverId and vehicleId
Trips are stored and analysed
\nAggregated insights and benchmarks become available in the FIA DSI platform
\nOnce ingested, data can be analysed across fleets, divisions, geographies and vehicle types without additional configuration.
\nThe FIA DSI API is not just an ingestion interface — it defines the structure used for all analytics.
\nConsistent identifiers and hierarchies are essential for reliable benchmarking.
\nBoth API-based ingestion and TSP integrations produce the same analytical model inside the FIA DSI.
\nDesign your integration with long-term trends and comparisons in mind.
\nThe FIA DSI is built on high-quality vehicle and trip data. There are two primary ways to provide data to the platform:
\nYou can send data directly to the FIA DSI using the endpoints described in this API documentation. This option is well suited if you:
\nalready collect vehicle or telematics data in your own systems,
\nwant full control over data flows and timing,
\nneed to combine multiple data sources before ingestion.
\nThe API supports structured ingestion of trips, vehicles, drivers and related metadata required for the FIA DSI’s analytics and benchmarking models.
\nIf you use a telematics platform, the FIA DSI can retrieve data directly from the source system. This option is ideal if you:
\nwant to minimise integration effort,
\nprefer a standardised and maintained connector,
\nwant a faster path to insights.
\nIn this setup, you grant the FIA DSI access to the relevant data source, and data retrieval, mapping and updates are handled as part of the integration.
\n","_postman_id":"01c7a363-a174-4070-8141-9c269a66296d"}]}