569 B
569 B
API Client Module
Purpose
This document explains how the API client authenticates and retries requests.
Current Behavior
- Access token is fetched before outbound request.
- Retry policy uses exponential backoff for transient failures.
Recent Increment (v2)
Added cache for tokens
- Token is cached in memory for a short TTL.
- Cache invalidates on 401 responses.
Operational impact
- Reduced auth latency for repetitive calls.
- Fewer token endpoint requests.
Limitations
- Single-process cache only.
- No distributed cache synchronization.