API & integrations

Your fleet data, in your systems.

The same REST API that powers the LYRA web and mobile apps can be used for integrations, so live location, trips, events and reports flow into your ERP, TMS, BI tools or customer portal.

Token authentication REST · JSON · HTTPS Role-based access
api · live fleetToken ✓ (Bearer)GET/api/live200 OK · JSON[ { "name": "Bus 12", "status": "moving", "speed": 42, "lat": 12.97, "lon": 77.59} ]Illustrative responseERPERPDispatch & billingTMSTMSPlanningBIBI dashboardDashboardsPortalCustomer portalCustomer status
What you can connect

Everything the apps use, available to your software.

Access is scoped to what each integration needs, and to the roles you grant.

Live fleet state

Current position, status and speed for every vehicle, on demand.

Trips, stops and events

The history of every trip and stop, plus ignition, overspeed, geofence and other events.

Reports on demand

Generate reports and take them as JSON, Excel, PDF or CSV.

Devices, drivers and users

Manage fleet records programmatically, within the roles you grant.

Geofences

Create and manage the zones that raise entry and exit alerts.

Work hours & area worked

For construction and agriculture: machine hours and area covered.

Routes & schedules

Scheduled routes, stops and passengers for school and staff transport.

Share links

Time-limited, read-only live-location links that open without a login, ideal for customer tracking pages.

How access works

From first call to first request.

01

Tell us your use case

What you want to connect, and the systems involved: ERP, TMS, BI, a customer portal.

02

We scope access with you

Roles, the data each integration needs, and a walkthrough of the endpoints with your engineers.

03

Sign in, get a token, integrate

Authenticate to receive a token, call the API over HTTPS and get JSON back.

Technical basics

What your engineers will want to know.

Need something not listed, like events pushed into your own systems? Integrations are built to order. Tell us what you need.

StyleREST over HTTPS, JSON responses
AuthenticationSign in to receive a token, sent as a Bearer token on each request
Access controlRole-based (admin, manager, user): a token only sees what its role and organisation allow
Live dataRequest current state on demand. Alerts also reach people as push notifications
ReportsJSON, Excel, PDF and CSV
DocumentationShared with your engineers when access is set up
Common integrations

Where teams connect it.

ERP & billing

Trip and utilisation data feeding invoicing, costing and asset records.

TMS & dispatch

Live vehicle state and ETAs alongside the plans your dispatchers already run.

BI & data warehouse

Trips, stops and events pulled on a schedule into your own analytics.

Customer-facing tracking

Share links or your own portal showing customers where their vehicle is.

Is there public API documentation?

Not published openly yet. We walk your engineers through the endpoints and fields when access is set up, so you get the detail that matters for your use case.

How does authentication work?

You sign in to receive a token and send it as a Bearer token with each request over HTTPS. What that token can see depends on the role and organisation it belongs to.

Can LYRA push events to my own server?

Alerts reach people as push notifications today. If you need events pushed into your own systems, integrations are built to order: tell us what you need and we will scope it.

Can I integrate my own hardware too?

Yes. LYRA reads data from 70+ device models, and that data is available through the same API alongside everything else.

Tell us what you want to connect.

A short note on your systems and the data you need is enough. Our team replies personally.