Rate Limits

Overview

The Trakkr API implements rate limiting to ensure fair usage and maintain stability for all users. Rate limits are applied on a per-API-key basis.

Rate Limit Tiers

API access requires the Scale plan ($399/mo) or higher. Your rate limit depends on your plan:

Per-Endpoint Limits

Different endpoints have different rate limits based on their computational cost. Write operations and resource-intensive endpoints have stricter limits.

Rate Limit Headers

Every API response includes headers to help you track your current rate limit status:

Handling Rate Limits

When you exceed the rate limit, the API returns a 429 Too Many Requests status code. Your application should handle this gracefully:

Exponential Backoff

Exponential backoff is a strategy where you progressively increase the wait time between retries. Adding random jitter prevents all clients from retrying at exactly the same time:

1# Implement exponential backoff in shell
2attempt=1
3max_attempts=5
4
5while [ $attempt -le $max_attempts ]; do
6  response=$(curl -s -w "%{http_code}" \
7    -H "Authorization: Bearer $TRAKKR_API_KEY" \
8    'https://api.trakkr.ai/get-brands')
9  
10  status=$(echo "$response" | tail -c 4)
11  
12  if [ "$status" -eq 200 ]; then
13    echo "Success!"
14    break
15  elif [ "$status" -eq 429 ]; then
16    sleep_time=$((2 ** $attempt))
17    echo "Rate limited. Retrying in ${sleep_time}s..."
18    sleep $sleep_time
19    attempt=$((attempt + 1))
20  else
21    echo "Error: $status"
22    break
23  fi
24done

Best Practices