The Quartix API: build your data, your way
QWS, the Quartix Web Services API, gives developers safe and secure access to live and historical vehicle tracking data. Pull real-time positions, trip history, driver scores and more into any system you build or already use.
"Meta" : { "Code" : 0 , "Message" : "" } ,
"Data" : [
{
"VehicleID" : 10421 ,
"DriverID" : 3088 ,
"LocationText" : "Birmingham, UK" ,
"Latitude" : 52.4862 ,
"Longitude" : -1.8904 ,
"Heading" : 180 ,
"Speed" : 34 ,
"LastEventDatetime" : "2026-02-25T14:32:00Z" ,
"LastEventDescription" : "Moving" ,
"NonTracking" : false
}
]
}
Current major version
Standard request and response format
Production integrations on QWS
Token-based authentication
Your fleet data, available as a JSON feed
QWS exposes the data behind your Quartix account through clean, predictable endpoints. Below is a summary of what's available. For the complete reference, including every parameter, response field, and example call, see the Swagger documentation.
Get the current location, speed, heading, and event status of every vehicle in your fleet, or just the ones you choose. Updated in near-real-time.
Pull complete journey records: start and end times, locations, distance, duration, and optional driving style data. Filter by vehicle, day range, or most-recent count.
Aggregated trip data grouped by day, month, site or vehicle. Ideal for periodic reporting, mileage rollups, and feeding finance or payroll systems.
List the drivers your account can see, with shift times and timezones. Pull each driver's current live location, even if they switch vehicles during a shift.
Pull driving style metrics alongside trip data, including harsh acceleration, braking, cornering, and speed scoring. Use it to feed coaching platforms or internal league tables.
List the regions, depots or operating areas a super-user can see. Useful for multi-site fleets that want to scope data by branch or operating region.
Authenticate, request, receive
QWS follows standard REST conventions. Your developers will be productive on day one: token-based authentication, predictable JSON responses, and clear request parameters.
Exchange credentials for an access token. Refresh tokens have a longer life so you don't re-authenticate on every request.
Content-Type : application/json
{
"Username" : "<your_user>" ,
"Password" : "<your_pass>"
}
Send the AccessToken as a header (or HTTPS-only cookie). Call any endpoint you're entitled to and pass filter parameters in the query string.
AccessToken : eyJhbGciOiJIUzI1NiIs...
# Optional query filters
?VehicleID[0]=10421
&VehicleID[1]=10422
Every response returns the same envelope: a Meta object for status and a Data array with the results. Parse, store, or pipe it wherever you need.
"Meta" : {
"Code" : 0 ,
"Message" : ""
} ,
"Data" : [...results... ]
}
What you can build with QWS
These are the patterns we see most often. Each scenario uses one or two endpoints and the result is data flowing automatically between Quartix and the system your business actually relies on.
Pipe driver hours straight into payroll
Pull a daily trip summary per driver, calculate shift hours from start and end times, and push the totals into your payroll or HR system. No spreadsheets, no manual checking.
GET /v2/api/vehicles/tripsummary
?StartDay=2026-02-01
&EndDay=2026-02-28
&GroupBy=day
AccessToken : <token>
# Response (truncated)
{
"Data" : [
{ "DriverID" : 3088 , "Distance" : 142.3 ,
"TravelTime" : "08:14:00" }
]
}
Build the dashboards your business actually needs
Schedule trip and trip-summary calls into Power BI, Tableau, Looker, or your own warehouse. Mash fleet activity together with sales, customer, or job data for reports that just aren't possible in any standalone telematics dashboard.
GET /v2/api/vehicles/trips
?TripStartDay=2026-02-24
&TripEndDay=2026-02-24
&Include=drivingStyle
AccessToken : <token>
# Response includes per-trip score
{
"Data" : [ {...trip, "DrivingScore" : 92 } ]
}
"Where's my driver?" features in your own app
Poll the live positions endpoint, filter by the vehicles assigned to a particular customer or job, and surface ETAs or live-tracking pages in your own customer portal, without exposing your full fleet.
GET /v2/api/drivers/positionlatest
?DriverID[0]=3088
AccessToken : <token>
{
"Data" : [ {
"Latitude" : 52.4862 ,
"Longitude" : -1.8904 ,
"Speed" : 34
} ]
}
Feed live behaviour data into coaching platforms
This is exactly how partners like Praiso build their AI coaching on top of Quartix. Pull driver-level scores and event counts, send them into a coaching workflow, and surface personalised content to each driver.
GET /v2/api/vehicles/tripsummary
?StartDay=2026-02-17
&EndDay=2026-02-23
&GroupBy=vehicle
&Include=drivingStyle
AccessToken : <token>
# Pipe into coaching campaigns
The same API that powers our integration partners
QWS isn't a sandbox or a side project. It's the same API powering MaxOptra route planning, FleetCheck compliance, Praiso driver coaching, Haulage Exchange load matching, and Courier Exchange dispatch. Battle-tested in production, stable, and well-documented.
- Real-time vehicle position data
- Historical trip and journey reports
- Driver behaviour scoring
- Geofencing alerts and events
Built for serious integrations, not just data exports
Manual exports, copy-paste between systems, and emailed CSVs are workarounds, not workflows. They're slow, error-prone, and they don't scale. QWS replaces all of that with a live, authenticated data feed your team can build into anything.
- Token-based authentication with refresh-token rotation
- Consistent JSON envelope across every endpoint
- Scoped access: only the data your account is entitled to
- Flexible filtering by vehicle, driver, date, and grouping
- Optional SFTP delivery for scheduled batch transfers
- Full Swagger documentation for your developers
POST /v2/api/auth
→ AccessToken + RefreshToken
# 2. Use it on every request
GET /v2/api/vehicles
AccessToken : eyJhbGciOiJIUzI1NiIs...
# 3. When it expires, refresh
POST /v2/api/refresh
RefreshToken : ...
→ New AccessToken
# 401 if invalid: handle and retry
Tokens can be passed as headers or HTTPS-only cookies. Refresh tokens can be revoked.
QWS is built to support real integrations, whether that's a customer's internal BI platform or one of our strategic partners. The same API that powers MaxOptra and FleetCheck is open to any of our customers who want to build something tailored to their business.
Oliver Smith, Head of Business Systems, Quartix
What you need to know
What does QWS stand for?
Quartix Web Services. It's the name we've used for the API since launch, and it's how our integration partners refer to it.
Who can access the Quartix API?
QWS is available to Quartix customers as part of an entitled subscription. Speak to our team and we'll confirm whether your account includes API access and what data is in scope.
What does the API actually expose?
Vehicles, drivers, real-time positions, complete trip history, trip summaries (with day, month, site or vehicle grouping), driving style metrics, and regions/sites. Each endpoint returns a consistent JSON envelope.
How is authentication handled?
Standard token-based auth. POST credentials to /auth, get an AccessToken plus a longer-lived RefreshToken. Pass the AccessToken on each request as a header or HTTPS-only cookie. Refresh tokens can be revoked at any time.
Is there full developer documentation?
Yes. Once access is provisioned we provide full Swagger/OpenAPI documentation with every endpoint, parameter, and response field, plus example calls. The Swagger UI also includes a "Try it out" sandbox for testing requests.
Can I receive data via SFTP instead?
Yes. If a live API isn't the right fit, we can set up direct data transfers to your database or via an SFTP site. Scheduled reports can also be exported automatically.
What are the rate limits?
Limits are set per account based on entitlement and intended use. We'll discuss expected request volumes during onboarding and configure the right rate plan for your integration.
Will my integration break when you update the API?
QWS is versioned (currently v2). Breaking changes go into a new major version with a clear migration window, so existing integrations keep working.
Talk to us about API access
Tell us what you're trying to build. We'll confirm the right API access for your account and get your developers the documentation they need.
- Secure, authenticated access to your fleet data
- Live positions, trips, scores, and geofence events
- Full Swagger documentation on request
- Same API powering MaxOptra, FleetCheck and Praiso
- Optional SFTP delivery for batch data transfers
Request API access
We'll be in touch to scope access and provide documentation.
No obligation. We'll be in touch within 1 business day.
Ready to build with the Quartix API?
QWS gives your developers secure access to live fleet data. Build the integration that actually fits your business.
