PEOPLEDEVELOPER TOOLSAI API MCP READY

iCIMS Careers API

Read job postings from any iCIMS career site as structured JSON. iCIMS is one of the largest enterprise applicant tracking systems, and its career sites come in several shapes — classic tenant portals, modern hosted sites, and custom domains. Give it a company name rather than a portal URL and it resolves that name to the site the company actually runs. Every posting carries both the date it was first posted and the date it was last updated, which is what makes a cutoff-based run return only what has changed since the last one.

MEDIAN LAGon demand
FIELDS8
TOTAL USERS3
MONTHLY ACTIVE2
TOTAL RUNS137
SUCCESS (30D)100.0%
RATINGno ratings yet
LAST MODIFIED2026-09-03
PUBLISHED2026-08

Input parameters

PARAMETERTYPEREQDEFAULTDESCRIPTION
startUrls array no — Career sites to collect. Classic tenant portals, modern hosted sites and custom domains are all detected automatically.
companies array no — A shortcut for classic tenants — a company name is expanded to its career-site URL, so you do not need to know the portal address.
newerThan string no — Return only jobs posted or updated since this moment. This is how a scheduled run collects changes instead of re-reading the whole board.
cutoffField string no updated Which date the cutoff compares against — first posted, or last updated.
includeDetails boolean no true On by default. Adds the full record — description, employment type and locations — rather than the index row alone.
descriptionFormat string no both Plain text, the original HTML, or both.
keywords array no — Keep only jobs matching at least one of these keywords.
maxJobsPerSite integer no 50 Stop after this many jobs from each career site. Set 0 to collect every live job. — drives your bill
maxJobs integer no 0 Stop the whole run after this many jobs across every site. 0 means no cap. — drives your bill
detailConcurrency integer no 5 How many job pages to fetch at once from a classic portal.
proxyConfiguration object no — Optional. Some employers restrict their career site to particular regions.

Output schema

FIELDTYPEDESCRIPTIONNULLABLE
title string Job title as the employer published it no
organization string Employer name no
locations_derived array Locations parsed from the posting, one entry per site yes
employment_type string Full time, part time, contract or intern, where the employer states it yes
date_posted string The employer's own first-published date yes
date_updated string The employer's own last-updated date, which drives cutoff runs yes
url string Canonical link to the posting on the employer's career site no
result_type string Whether the row is a job record or a career-site index entry no

Code

Every open role at one employer, as JSON

curl -X POST "https://api.apify.com/v2/acts/johnvc~icims-careers-api/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{ "companies": ["rambus"], "maxJobsPerSite": 0 }'

Only what changed since yesterday

curl -X POST "https://api.apify.com/v2/acts/johnvc~icims-careers-api/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{ "companies": ["rambus"], "newerThan": "2026-08-31", "cutoffField": "updated" }'

What people use it for

  • Building a list of companies using iCIMS
  • Watching an enterprise employer's board for new requisitions
  • Backfilling a job board from enterprise ATS sites
  • Change detection on an employer's postings using their own timestamps
  • Sales prospecting on enterprise hiring activity

More sources for Hiring signals and talent intelligence →

Alternatives

Greenhouse Job Board API — same job for Greenhouse boards, with published compensationours Ashby Job Board API — growth-stage companies rather than enterpriseours Workday Career Sites API — the other large enterprise ATSours Oracle Fusion Recruiting and Taleo Jobs API — Oracle Fusion Recruiting and legacy Taleoours