Introduction
Authentication & Rate Limiting
POST
The Travtus API requires every request to be authenticated using a Bearer token. Tokens are obtained via the OAuth 2.0Documentation Index
Fetch the complete documentation index at: https://docs2.travtus.com/llms.txt
Use this file to discover all available pages before exploring further.
client_credentials grant using the credentials provided to you by Travtus.
Request an access token
POST your credentials to the token endpoint to receive an access token valid for 60 minutes.
Request an Access Token
Request body (application/x-www-form-urlencoded)
Your API client ID.
Your API client secret.
Must be
client_credentials.Response
Bearer token to include in the
Authorization header of all subsequent API requests.Always
Bearer.Seconds remaining until the token expires. Up to 3600 on a fresh token (60 minutes).
Call the API
Include theaccess_token in the Authorization header of every request.
The bearer token is valid for 60 minutes (3600 seconds). Once it expires, you must re-authenticate to obtain a new token. Requesting a new token on every API call is unnecessary and may result in throttling.
Rate Limiting
The Travtus API enforces rate limits to ensure platform stability and fair usage across all clients. Exceeding a limit returns HTTP 429 Too Many Requests. Implement exponential backoff when retrying after a 429 response.Token endpoint (/oauth2/token)
| Limit | Value |
|---|---|
| Sustained rate | 100 requests/second |
| Burst | 200 requests |
All other API endpoints
| Limit | Value |
|---|---|
| Sustained rate | 10,000 requests/second |
| Burst | 5,000 requests |
How limits are applied
- Limits are applied per API key at the API Gateway level.
- The burst limit allows short spikes above the sustained rate.
- Clients should implement retry logic with exponential backoff on 429 responses.

