bamboohr-rate-limits

# BambooHR Rate Limits ## Overview BambooHR does not publish exact rate limits, but the API returns `503 Service Unavailable` with a `Retry-After` header when you exceed them. This skill covers detection, backoff, request optimization, and queue-based throttling. ## Prerequisites - BambooHR API client configured - Understanding of async/await patterns ## Instructions ### Step 1: Understand BambooHR Rate Limiting Behavior BambooHR rate limiting details: | Signal | Value | Description | |--------|-------|-------------| | HTTP Status | `503` | Primary rate limit signal | | `Retry-After` header | seconds (e.g., `30`) | How long to wait before retrying | | `X-BambooHR-Error-Message` | varies | May contain rate limit detail | | HTTP Status `429` | rare | Some endpoints return 429 for employee count limits | **Key insight:** BambooHR uses `503` (not `429`) for rate limiting. Failed authentication attempts also count toward rate limits, so ensure your API key is valid before making many requests. ### Step 2: Implement Retry-After Aware Backoff ```typescript import { BambooHRApiError } from './client'; interface RetryConfig { maxRetries: number; baseDelayMs: number; maxDelayMs: number; } const DEFAULT_RETRY: RetryConfig = { maxRetries: 5, baseDelayMs: 1000, maxDelayMs: 60_000, }; async function withBambooHRRetry<T>( operation: () => Promise<T>, config = DEFAULT_RETRY, ): Promise<T> { for (let attempt = 0; attempt <= config.maxRetries; attempt++) { t...