Pull candidate pipeline and stage data from the iCIMS REST API and handle rate limits and pagination

Steps

1. Authenticate using OAuth 2.0 by obtaining an access token from the iCIMS authorization server; iCIMS also supports HMAC authentication for some legacy integrations but OAuth 2.0 is the recommended method.
2. Construct API requests using HTTPS — TLS 1.2 or higher is required; all traffic on lower TLS versions is rejected.
3. Implement pagination for list endpoints; iCIMS list responses include pagination metadata and can be filtered by attributes such as applicant workflow person ID to scope results.
4. Respect the default rate limit of 10,000 API calls per day per customer; monitor the X-RateLimit-Reset and remaining calls headers included in each response to track usage and throttle requests proactively.
5. Design your JSON parsing to treat response payloads as key-value maps and ignore unknown keys — iCIMS may add new JSON fields at any time without versioned notice; strict schema validation will break on additions.
6. Handle 429 Too Many Requests responses with exponential backoff and use the X-RateLimit-* headers to determine the reset time before retrying.