Authenticate with OAuth 2.0 and obtain a scoped access token permitting read access to job and applicant workflow resources.
GET the list of active jobs by querying the jobs resource endpoint, applying filters for job status to return only open requisitions; page through results using the pagination metadata in each response.
For each job, GET the associated applicant workflows to retrieve candidate stage, disposition, and source attribution data.
Merge job and applicant data in your pipeline, normalizing iCIMS-specific status codes and stage labels into your dashboard's standard vocabulary.
Schedule incremental sync runs using a last-modified or created-after filter parameter where supported to reduce API call volume on repeated syncs rather than pulling the full dataset each time.
Surface data in the dashboard with clearly labeled iCIMS-sourced indicators so that the iCIMS tenant context is preserved for drill-down and audit purposes.
Known gotchas
iCIMS does not guarantee a stable ordering of results across paginated requests when new records are added mid-query; use a cursor or last-modified filter rather than offset-based pagination for reliable incremental sync.
Applicant workflow stage labels are configured per iCIMS account and are not standardized across tenants; maps built for one customer's stage names will need reconfiguration for another.
The 10,000 daily API call limit can be exhausted quickly when fetching applicant details for large active job pools; design the dashboard refresh schedule to stay well within limits using batch windows.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp