navan-rate-limits

# Navan Rate Limits ## Overview Navan does not publicly document its API rate limits. Developers typically discover thresholds empirically when bulk data pulls or batch operations begin returning HTTP 429 responses. This skill implements defensive rate-limiting patterns that adapt to server responses rather than relying on fixed quotas — inspecting response headers, applying exponential backoff with jitter, and queuing requests to prevent flooding. ## Prerequisites - Active Navan OAuth 2.0 credentials (see `navan-install-auth`) - Node.js 18+ (examples use native fetch) - Understanding of HTTP 429 status code and Retry-After header semantics ## Instructions ### Step 1: Build an Adaptive Retry Wrapper ```typescript interface RetryOptions { maxRetries: number; baseDelayMs: number; maxDelayMs: number; } async function navanFetch( url: string, options: RequestInit, retry: RetryOptions = { maxRetries: 5, baseDelayMs: 1000, maxDelayMs: 30000 } ): Promise<Response> { let lastError: Error | null = null; for (let attempt = 0; attempt <= retry.maxRetries; attempt++) { const response = await fetch(url, options); // Log rate limit headers when present (undocumented but sometimes returned) const remaining = response.headers.get('X-RateLimit-Remaining'); const limit = response.headers.get('X-RateLimit-Limit'); if (remaining !== null) { console.log(`Rate limit: ${remaining}/${limit} remaining`); } if (response.status !== 429) return r...