LocoNav
LocoNav is an AI- and IoT-powered GPS vehicle tracking and smart fleet management platform used across 50+ countries, integrating 2,200+ device and sensor types to track vehicles and assets in real time. Its LocoNav Integration API exposes REST endpoints and webhooks for fleet telematics: telematics data (sensor readings, GPS location, distance, timelines, video and live streams), CRUD management of drivers, vehicles, trips, geofence polygons and users, driver-vehicle assignment, vehicle scorecards, immobilization, live share links, and alert subscriptions. Real-time alert and live-location webhooks push events such as overspeed, harsh braking/acceleration, geofence, fatigue, crash, fuel-theft, anti-theft and device-offline. Authentication is a user-level token in the User-Authentication header; all listing endpoints are paginated and time parameters use epoch seconds.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles LocoNav the way a machine reads it — 30 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — LocoNav scores 47.2/100 (developing), with a separate agent-readiness read of 30/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from LocoNav's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/loconav/"
title="LocoNav on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/loconav.svg"
alt="LocoNav Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/loconav/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/loconav/"
title="LocoNav on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/loconav/card.svg"
alt="LocoNav Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile LocoNav
Each block below is one kind of artifact we hold for LocoNav. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 12
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
LocoNav Alert Subscriptions API
With our Alert subscription APIs, you can manage the alerts effectively on a platform
LocoNav Alerts API
The Alerts API from LocoNav — 2 operation(s) for alerts.
LocoNav Alerts Subscriptions API
The Alerts Subscriptions API from LocoNav — 1 operation(s) for alerts subscriptions.
LocoNav Drivers API
Efficient driver management is essential for the optimal operation of a fleet.
Leveraging the capabilities of LocoNav REST APIs, fleet managers can seamlessly create, ...
LocoNav Mobilization API
The Mobilization API from LocoNav — 2 operation(s) for mobilization.
LocoNav Polygon (Geofence) API
A geofence is a virtual boundary, often a rectangular bounding box, created using mapping software with specified latitude and longitude coordinates. Integra...
LocoNav Trips API
The Trips API from LocoNav — 3 operation(s) for trips.
LocoNav Users API
The Users API from LocoNav — 1 operation(s) for users.
LocoNav Vehicles API
Loconav's Vehicle APIs offer developers a powerful toolkit for real-time fleet management. The Fetch Vehicle Details API provides comprehensive vehicle insights, while the La...
LocoNav Vehicles / Telematics API
Thes APIs allows you to access telematics data for vehicles, enabling you to retrieve real-time information and history about their status, location, and various sensor readi...
LocoNav Video Telematics VT / Live Stream API
The Video Telematics VT / Live Stream API from LocoNav — 3 operation(s) for video telematics vt / live stream.
LocoNav Video Telematics VT / Videos API
The Video Telematics VT / Videos API from LocoNav — 2 operation(s) for video telematics vt / videos.
Scroll within the panel for all 12 ·
Open Collections 13
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONLocoNav Integration Alert Subscriptions API
OPEN COLLECTIONLocoNav Integration Alert Subscriptions Alerts API
OPEN COLLECTIONLocoNav Integration Alert Subscriptions Drivers API
OPEN COLLECTIONLocoNav Integration Alert Subscriptions Mobilization API
OPEN COLLECTIONLocoNav Integration Alert Subscriptions Trips API
OPEN COLLECTIONLocoNav Integration Alert Subscriptions Users API
OPEN COLLECTIONLocoNav Integration Alert Subscriptions Vehicles API
OPEN COLLECTIONScroll within the panel for all 13 ·
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Loconav Rate Limits
RATE LIMITSEvent Specifications 2
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
LocoNav Webhooks
AsyncAPI description of LocoNav alert and live-location webhooks derived from the published Postman webhook examples. LocoNav POSTs these events to a partner-registered receiver...
ASYNCAPILoconav Webhooks
ASYNCAPISecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for LocoNav — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 4
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/loconav · machine-readable index on apis.io
This is an independent, third-party profile of LocoNav, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.