Rate Limits

Endpoint Limits

Response Headers

When you hit the rate limit, the response includes a Retry-After header:

The /api/shorten endpoint also returns these headers on all responses:

Handling 429 Responses

When rate limited, you receive a 429 status with this body:

{
  "error": "Too many requests"
}

// Headers:
// Retry-After: 45

Best Practices

async function apiCallWithRetry(fn: () => Promise<Response>, maxRetries = 3) {
  for (let attempt = 0; attempt < maxRetries; attempt++) {
    const res = await fn();

    if (res.status === 429) {
      const retryAfter = parseInt(res.headers.get('Retry-After') || '60');
      console.log(`Rate limited. Retrying in ${retryAfter}s...`);
      await new Promise(r => setTimeout(r, retryAfter * 1000));
      continue;
    }

    return res;
  }

  throw new Error('Max retries exceeded');
}

Tips for Staying Within Limits

• Cache responses: List results and link data can be cached on your end to reduce API calls
• Use webhooks for real-time data, Instead of polling for click events, subscribe to link.click webhooks
• Batch operations in the dashboard, The dashboard supports bulk operations (import, export, tag) without counting against API limits
• Use pagination efficiently, Fetch larger pages (up to 100 items) instead of many small pages
• Respect Retry-After, Always wait the specified time before retrying, or you risk progressive penalties