LemursEye
Documentation
Platform

Integration Hub: how it works

Your fleet data, in the systems that run your business

The Integration Hub reads the same event stream every other component reads and turns it into outputs for systems outside LemursEye. You write formulas over trips, idle time, alerts and fuel (a rate per kilometre, a surcharge after hours, a rounding rule), shape the result to the target's schema, and connect it: Odoo invoice lines and analytic accounts, a webhook to your own software, a scheduled file to a government tracking portal. Every delivery is logged and can be replayed. Nothing about your fleet is locked inside our screens.

The parts

1. Event stream

trips · alerts · summary · positions

Every trip with its measured distance and engine-on idle, every alert, every day's totals, per vehicle and per tenant, as they happen or in batches. The REST API serves the same data today.

2. Formulas (roadmap)

formula · per tenant · versioned

Your arithmetic over the stream: billable_km = distance_km × 1.05, after_hours_fee = km_after_hours × 2.5, waiting = idle_h > 1 ? idle_h − 1 : 0. Units, rounding and thresholds you control, tested against yesterday before going live.

3. Output shaping (roadmap)

template · json · csv · xml

Map fields to the target's schema with a template: an Odoo invoice line, a CSV a ministry accepts, the JSON your dispatcher app expects. Preview the exact payload before switching it on.

4. Connectors (roadmap)

odoo · webhook · mqtt · sftp · email

Odoo through its standard XML-RPC API: invoice lines, fleet odometers, analytic accounts. Signed webhooks to any URL. MQTT for control rooms. Files by SFTP or email on a schedule.

5. Government feed (roadmap)

scheduled · signed · auditable

Where an authority requires vehicle tracking data, a scheduled, signed feed in its format, per vehicle, with proof of delivery. One connector per authority, maintained once for every customer.

6. Audit & replay (roadmap)

deliveries · retries · replay

Every delivery recorded with payload, response and time; failures retried with backoff; any window replayable after a target outage or a formula fix.

Build on it

The same data is available over the API and the live socket.