How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

TRONITY Vehicle Data API

The Vehicle Data API from TRONITY — 7 operation(s) for vehicle data.

TRONITY Vehicle Data API is one of 6 APIs that TRONITY publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Vehicle Data. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 7 operations across 7 paths, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://api.tronity.tech.

7 operations 7 paths 4 schemas 7 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.tronity.tech
Authentication
HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 1

TRONITY Vehicle Data API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth).

  • bearerAuth — OAuth2 Bearer access token obtained from POST /oauth/authentication. Available scopes include readvin, readvehicleinfo, readodometer, readcharge, readbattery,…

Paths & Operations 7

Across 7 paths, the API surfaces 7 operations — 7 GET. Each is listed below with its method, path, parameters, and response codes.

Vehicle Data 7
GET
/v1/vehicles/{vehicleId}/odometer
Get odometer from the vehicle
vehicleControllerOdometer 1 param → 200
GET
/v1/vehicles/{vehicleId}/location
Returns the last known location of the vehicle in geographic coordinates
vehicleControllerLocation 1 param → 200
GET
/v1/vehicles/{vehicleId}/bulk
Read bulk data based on vehicle scope
vehicleControllerBulk 1 param → 200
GET
/v1/vehicles/{vehicleId}/records
Retrieve many Record
getManyRecords 1 param → 200
GET
/v1/vehicles/{vehicleId}/trips
Retrieve many Trip
getManyTrips 1 param → 200
GET
/v1/vehicles/{vehicleId}/idles
Retrieve many Idle
getManyIdles 1 param → 200
GET
/v1/vehicles/{vehicleId}/sleeps
Retrieve many Sleep
getManySleeps 1 param → 200

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are Record (18 properties), Bulk (8 properties), Location (3 properties), Odometer (2 properties). Each schema is shown below with its type and property counts.

Record
object
18 properties
Location
object
3 properties
Bulk
object
8 properties
Odometer
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tronity-vehicle-data-api-openapi.yml Raw ↑

Other APIs TRONITY publishes across the network.

TRONITY Authentication API
TRONITY Charging & Battery API
TRONITY Commands API
TRONITY Vehicles API
TRONITY Webhooks API
Where this information came from

This is an independent, third-party profile of TRONITY Vehicle Data API, 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.