TravelPerk · Rate Limits

Travelperk Rate Limits

The TravelPerk Open API applies per-application rate limiting to protect the platform, returning HTTP 429 when limits are exceeded. List endpoints (trips, invoices, invoice lines, cost centers) are paginated to bound result sizes. Specific per-endpoint request-per-minute and daily quota values are not publicly published and are not reconciled in this artifact.

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

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

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

Tagged areas include Business Travel, Travel Management, Expenses, Invoices, and Bookings.

3 Limits Throttle: 429
Business TravelTravel ManagementExpensesInvoicesBookingsRate LimitingQuotasThrottling

Limits

Requests Per Application application
requests
see provider documentation
Per-application request rate limit; specific value not publicly published.
Pagination endpoint
records
see provider documentation
List endpoints are paginated; page size and max limit per page vary by endpoint.
SCIM Provisioning application
requests
see provider documentation
SCIM 2.0 endpoints (Premium) use a separate token and may have distinct limits.

Policies

Tiered Access
API, SCIM, and webhook access is gated by plan tier (e.g. Premium / Pro).
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.

Sources