hex-rate-limits

# Hex Rate Limits ## Overview Hex's API enforces tight limits on project run triggers (20 per minute, 60 per hour) while leaving read operations like status checks and project listing largely unthrottled. Data teams scheduling batch analytics runs or triggering parameterized notebooks from CI/CD pipelines must carefully manage the hourly cap, since a single pipeline triggering 15 projects can consume a quarter of the hourly budget. Polling run status is free, but triggering runs is the bottleneck that shapes integration architecture. ## Rate Limit Reference | Endpoint | Limit | Window | Scope | |----------|-------|--------|-------| | RunProject (trigger) | 20 req | 1 minute | Per API token | | RunProject (trigger) | 60 req | 1 hour | Per API token | | GetRunStatus | No hard limit | - | Per API token | | ListProjects | No hard limit | - | Per API token | | CancelRun | No hard limit | - | Per API token | ## Rate Limiter Implementation ```typescript class HexRateLimiter { private minuteTokens: number = 20; private hourlyTokens: number = 60; private lastMinuteRefill: number = Date.now(); private lastHourlyRefill: number = Date.now(); private queue: Array<{ resolve: () => void }> = []; async acquire(): Promise<void> { this.refill(); if (this.minuteTokens >= 1 && this.hourlyTokens >= 1) { this.minuteTokens -= 1; this.hourlyTokens -= 1; return; } return new Promise(resolve => this.queue.push({ resolve })); } private refill() ...