FleetAccess integration
Lightweight telematics API for real-time vehicle location, driver ID and trip-level data ingestion.
What syncs between FleetAccess and Transportial
- Into Transportial
Tracking units
Every FleetAccess object becomes a board computer in Transportial, with its IMEI. You link each one to its truck once; units your account no longer returns are archived.
- Into Transportial
Positions and sensor data
Every position record, not just the latest, with speed, odometer, fuel level and fuel used, RPM, engine hours, coolant temperature, battery voltage, weight, temperatures, Thermo King reefer values, tyre pressures, ignition and the tachograph state of both drivers.
- Into Transportial
Tachograph activities and remaining driving time
Driving, work, availability and rest periods become driver activities with start and end time and position. Remaining daily, weekly and two-week driving time, reduced rests and the working week are updated on the driver.
- Into Transportial
Remote tachograph files
Finished remote downloads of driver cards and vehicle units are collected as .ddd files, stored as documents, parsed and checked for a valid signature.
- Into Transportial
Infringements
Tachograph infringements become alerts on the driver, matched by card number: serious infringements as errors, the rest as warnings.
- Into Transportial
Drivers and driver assignments
Drivers are created with name, mobile number and tachograph card. When a driver starts or stops on a vehicle, Transportial links or unlinks them.
- Into Transportial
Vehicle timeline
Completed journeys with from and to address, distance, duration and fuel; harsh driving and idling events; refuels and fuel losses; border crossings with driving, working and resting time per country; geozone entries and exits; and eco-driving scores such as fuel rate, CO2 and overspeed share.
How to connect FleetAccess
Get an API key for your FleetAccess account. It is the only credential the integration needs.
Add the FleetAccess integration in Transportial and enter the key. Units and drivers are imported on the first sync.
Link each imported unit to its truck. From then on positions, sensor values and timeline events land on that vehicle.
Sync frequency and limits
- Positions every 2 minutes, tachograph state every 5 minutes, driver assignments every 10 minutes, remaining driving times and driving events every 15 minutes.
- Geozone visits and fuel events every 30 minutes, journeys and border crossings every hour, tachograph files every 2 hours, units every 3 hours, drivers, eco-driving and infringements every 6 hours.
- Each feed keeps its own sync position, and data that is read twice is not stored twice.
- If FleetAccess answers with a rate limit or a server error, the same time window is retried on the next run, so there are no gaps.
- If your account isn’t licensed for a feature, only that feed stops; the others keep running.
Typical use case
A haulier with FleetAccess units wants to plan with real driving times. Planners see each driver’s remaining daily and weekly driving time next to the trip, tachograph activities show up on the driver’s timeline, and infringements arrive as alerts the same day. The .ddd files from remote downloads are filed automatically under the right driver, ready for the legally required archive.
Frequently asked questions
Can Transportial send trips or messages to FleetAccess?
No. The integration reads data from FleetAccess only; drivers receive their trips in the Transportial driver app.
Are vehicles created automatically?
No. Each FleetAccess unit is imported as a board computer, and you link it to the right truck once. Drivers, on the other hand, are created automatically.
Does Transportial start remote tachograph downloads?
No. FleetAccess runs the downloads; Transportial collects the finished driver-card and vehicle-unit files every two hours and files them under the driver by card number.
Which driving-time limits are shown?
Remaining daily, weekly and two-week driving time (the 90-hour limit of EU Regulation 561/2006), reduced daily rests left, days driven over nine hours and the working week, as calculated by FleetAccess.
Connect FleetAccess to your TMS
Transportial’s integration framework links your operation to FleetAccess and any other system you run.