TRONITY · Rate Limits

Tronity Rate Limits

The TRONITY Platform API is OAuth2-secured and access is constrained both by the scopes a vehicle owner grants and by the subscription tier (per vehicle, per administrator). TRONITY does not publish specific numeric request-per- minute or per-day limits in its public help center, and live vehicle reads are also bounded by how frequently the underlying OEM telematics can be polled. Specific per-endpoint and per-account limits are not reconciled in this artifact.

Tronity Rate Limits is the machine-readable rate-limit profile for TRONITY on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring requests, scopes, and vehicles.

The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Connected Car, EV, Telematics, Fleet, and Vehicle Data.

4 Limits Throttle: 429
Connected CarEVTelematicsFleetVehicle DataRate LimitingQuotasThrottling

Limits

Requests Per Account account
requests
see provider documentation
Public help center does not publish a numeric RPM/RPD; verify in the platform docs.
Per-Vehicle Polling vehicle
requests
see provider documentation
Read frequency for live data is bounded by OEM telematics polling cadence.
Scope-Constrained Access vehicle
scopes
granted scopes only
Each request is limited to the read/write scopes the vehicle owner granted (e.g. read_battery, write_charge_start_stop).
Subscription Tier account
vehicles
by plan
Number of vehicles and administrator seats available is set by the subscription tier.

Policies

Scope Enforcement
Calls outside the granted OAuth2 scopes are rejected regardless of rate.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.

Sources