posthog-rate-limits

# PostHog Rate Limits ## Overview PostHog rate limits apply to private API endpoints authenticated with a personal API key (`phx_...`). Public capture endpoints (`/capture/`, `/batch/`, `/decide/`) are **not** rate limited. Understanding which endpoints have limits is critical to avoiding 429 errors. ## Prerequisites - PostHog personal API key (`phx_...`) for admin endpoints - Understanding of which endpoints you call and how often - `posthog-node` or direct API usage ## PostHog Rate Limit Tiers | Endpoint Category | Rate Limit | Examples | |-------------------|-----------|----------| | Event capture (`/capture/`, `/batch/`) | **No limit** | `posthog.capture()`, batch ingestion | | Feature flag decide (`/decide/`) | **No limit** | Client-side flag evaluation | | Analytics API (insights, persons, recordings) | **240/min, 1200/hour** | Trend queries, person lookup | | HogQL query API (`/api/projects/:id/query/`) | **1200/hour** | Custom SQL queries | | Feature flag local evaluation polling | **600/min** | Server SDK flag definition fetch | | All other private endpoints | **240/min, 1200/hour** | Feature flag CRUD, cohorts, annotations | ## Instructions ### Step 1: Implement Exponential Backoff with Retry-After ```typescript async function postHogApiCall<T>( url: string, options: RequestInit, maxRetries = 5 ): Promise<T> { for (let attempt = 0; attempt <= maxRetries; attempt++) { const response = await fetch(url, { ...options, headers: { ...