Tive · Rate Limits

Tive Rate Limits

The Tive Public API (v3) is a Bearer-token-authenticated REST API. Tive's developer documentation does not publish specific numeric rate limits for the public API. Known operational constraints include short-lived bearer tokens (1 hour / 3600 second lifetime, after which a 401 is returned and a new token must be requested) and list pagination (e.g. the List Devices endpoint returns up to 50 devices per request). Any per-account request-rate or throttling thresholds are not documented and are not reconciled in this artifact.

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

It captures 3 rate-limit definitions, measuring seconds, items, and requests.

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

Tagged areas include Supply Chain, Shipment Visibility, Logistics, IoT, and Trackers.

3 Limits Throttle: 429
Supply ChainShipment VisibilityLogisticsIoTTrackersReal TimeRate LimitingQuotasThrottling

Limits

Bearer Token Lifetime token
seconds
3600
Tokens expire after 1 hour; expired tokens return 401 and must be re-issued via POST /authenticate.
List Devices Page Size request
items
50
The List Devices endpoint returns up to 50 devices per request with pagination support.
Request Rate account
requests
see provider documentation
No numeric per-account request-rate limit is published in Tive's developer documentation.

Policies

Token Refresh
Re-authenticate via POST /authenticate when a token expires (401) to obtain a fresh bearer token.
Pagination
Page through list endpoints (e.g. devices) using the documented pagination support rather than assuming full result sets.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses if encountered.

Sources