Integrations
REST API, webhooks and scheduled exports
Telematics data is worth more inside the systems a business already runs. The platform exposes a REST API for reads, webhooks for push, and scheduled exports for the reporting layer, so trip, position, engine and sensor data can reach an ERP, a billing run or a payroll process without manual re-entry.
Prefer the main Yipii pages?
Who this is for
- IT teams integrating telematics into an existing ERP
- Operators automating billing from trip and mileage data
- Developers building internal dashboards over fleet data
- Businesses replacing a manual mileage or timesheet process
REST API
The API covers vehicles, trips, positions, geofences, drivers, alerts and sensor readings. Requests are authenticated per account. Responses are JSON. The API is read-oriented for reporting workloads and supports the entity and date-range filters that reporting actually needs.
- Vehicle, driver and geofence records
- Trip and stop history with start, end, distance and duration
- Raw position history for route reconstruction
- Engine and sensor readings from CAN bus, OBD and BLE devices
Webhooks
Webhooks push events as they happen, which removes the need to poll. Geofence entry and exit, ignition state change, alert conditions and sensor thresholds can each trigger a callback to an endpoint the customer controls.
- Geofence entry and exit
- Ignition on and off
- Alert conditions including tamper, speed and battery voltage
- Sensor threshold breaches, including temperature excursions
Scheduled exports
Where an integration is not warranted, scheduled email reports deliver the same data on a fixed cadence. This suits monthly mileage claims, per-vehicle billing summaries and management reporting that a person reads rather than a system consumes.
- Fixed daily, weekly or monthly cadence
- Per-vehicle, per-driver or per-group scope
- Mileage and trip summaries suited to tax and billing records
What the data comes from
Data quality depends on the install. An OBD device reports position, ignition and the engine parameters the vehicle exposes on the diagnostic port. A hardwired install with a direct CAN connection reports a wider parameter set, including fault codes, fuel, coolant and oil temperature. BLE sensors add temperature, humidity, door state and light. The API surface is the same; the parameters available per vehicle depend on how that vehicle was fitted.
- OBD: position, ignition, diagnostic port parameters
- Hardwired CAN: fault codes, fuel, coolant and oil temperature
- BLE sensors: temperature, humidity, door state, light
- Driver ID: RFID, iButton, hardwired reader, BLE tag, app
When Yipii is not the right fit
Cases where you should look at something else, or budget for a second system alongside this one.
- A prebuilt connector for a specific ERP is expected. Integration is through the REST API and webhooks, so it needs development work on the customer side or through their integrator.
- Sub-second telemetry streaming is required. Reporting intervals are configurable, but the platform is built for fleet operations rather than high-frequency streaming.
- Write-heavy control of vehicles through the API is expected. The API is oriented to reads and reporting.
Questions
- Does the platform have a REST API?
- Yes. The REST API covers vehicles, trips, positions, geofences, drivers, alerts and sensor readings, authenticated per account and returning JSON.
- Are webhooks supported, or is polling required?
- Webhooks are supported. Geofence entry and exit, ignition state changes, alert conditions and sensor threshold breaches can push to a customer-controlled endpoint, which removes the need to poll.
- Can trip data be pushed into an accounting or ERP system?
- Yes, through the REST API or webhooks. Scheduled email exports are available where a full integration is not warranted. Integration work is carried out by the customer or their integrator against the documented API.
- Which engine parameters are available through the API?
- It depends on the installation. OBD devices expose the parameters available on the vehicle diagnostic port. A hardwired CAN bus install exposes a wider set, including fault codes, fuel, coolant temperature and oil temperature. BLE sensors add temperature, humidity, door state and light.
Request API documentation
Yipii Ltd has provided vehicle tracking and fleet telematics in Malta since 2010, previously as Dazzle Panel and DP:Tracking. The platform, alerts and tracking run 24/7. Human support is available during business hours.
Written and maintained by the Yipii team, Malta.