Transit · Rate Limits

Transitapp Rate Limits

Transit publishes explicit rate limits for its free API tier: up to 5 requests per minute and 1,500 requests per month per access key. These are hard caps on the free tier; exceeding them requires arranging higher limits with Transit's partnerships team, whose ceilings are negotiated rather than published. Because real-time transit data changes frequently, Transit recommends pacing polling (for example, refreshing a departure board every 10-30 minutes) to stay within the free monthly budget.

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

It captures 3 rate-limit definitions, measuring requests.

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

Tagged areas include Transit, Public Transportation, Real-Time, Rate Limiting, and Quotas.

3 Limits Throttle: 429
TransitPublic TransportationReal-TimeRate LimitingQuotas

Limits

Free Tier Requests Per Minute apiKey
requests
5 per minute
Hard cap on the free access-key tier.
Free Tier Requests Per Month apiKey
requests
1500 per month
Hard monthly cap on the free access-key tier.
Partner / Higher Volume account
requests
negotiated
Higher rate and monthly limits arranged with partners@transit.app; not published.

Policies

Pacing Recommendation
Transit recommends refreshing real-time data on an interval (e.g. every 10-30 minutes for departure boards) to stay within the free monthly budget.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.
Caching
Cache relatively static responses (route details, available networks) and only re-poll real-time departures as needed to conserve quota.

Sources