iCIMS Jobs API.
A developer’s reference. iCIMS Talent Cloud API is partner-only - no self-serve credentials, no public sandbox. Here is how iCIMS careers sites actually surface postings, why the internal endpoint is shape-sensitive to iCIMS module versions, and when reaching for a unified jobs API skips the partner-program path entirely.
On this page
The short answer
iCIMS does not offer a public, self-service jobs API. The iCIMS Talent Cloud API at developer.icims.com is gated behind the iCIMS Partner Program - you apply, get approved (typically with a sponsoring iCIMS customer), and receive per-customer-scoped credentials. No API key is self-mintable. No public sandbox. No public OpenAPI spec.
What every iCIMS customer does have is a public careers site at <company>.icims.com or a vanity domain like jobs.<company>.com that proxies iCIMS underneath. The careers site renders postings client-side from an internal JSON endpoint. The data is reachable, but the JSON shape varies by iCIMS module (Recruit, Onboard, Connect, Apply) and changes between iCIMS releases.
What the Talent Cloud API is
iCIMS Talent Cloud is a suite, not a single product. The pieces are:
- Recruit - the ATS itself. Jobs, requisitions, candidates, applications, pipeline stages.
- Onboard - new-hire workflows that trigger after an offer is accepted.
- Connect - the candidate-relationship CRM, for nurturing passive talent.
- Marketplace - partner integrations that plug into the rest.
The Talent Cloud API exposes records across these surfaces. Access is partner-only, the partner program requires a sponsoring iCIMS customer, and even after approval the credentials are scoped per-customer rather than multi-tenant. That structure fits per-customer integrations (a recruiting CRM that syncs candidates with one iCIMS customer), not aggregation.
The public surface (and why it's tricky)
Every iCIMS customer with public hiring has a careers site - either <company>.icims.com or a customer- owned vanity domain running iCIMS embeds. The site renders job postings client-side from an internal JSON endpoint shaped like /jobs/intelliservices.
That internal endpoint is the actual public data surface. Cleaner than HTML scraping (returns JSON directly), but undocumented, version-sensitive across iCIMS modules, and rate-limited per domain. A scraper hitting many customer subdomains needs IP rotation and careful retry logic.
Vanity domains and iCIMS embeds
Many enterprise iCIMS customers prefer a vanity domain pattern - jobs.<company>.com or careers.<company>.com - that proxies iCIMS underneath. Siemens, PepsiCo, Lowe’s, Verizon, Bayer, and Nestle all run this pattern.
From the outside, a vanity domain looks like a custom build. Under the hood it’s still iCIMS, hitting the same internal endpoint with the same shape rules. Any iCIMS integration has to handle both URL patterns -<company>.icims.com and the vanity- domain proxy - to capture the full customer base.
Why scraping breaks at scale
Discovery. iCIMS doesn’t publish a customer list. The <company>.icims.com pattern makes discovery partially possible (you crawl from known slugs), but vanity-domain customers are only discoverable by inspecting their careers pages and detecting iCIMS embeds in the source.
Module shape drift. The internal JSON endpoint’s response shape varies depending on which iCIMS module the customer has enabled - Recruit vs Onboard vs Connect vs Apply. iCIMS releases also shift the shape between major versions without developer notice.
Rate limits + CDN protection. iCIMS runs per-domain rate limits plus CDN-level abuse protection. Scraping many customer subdomains from one IP gets blocked quickly. IP rotation, polite cadences, and careful retry logic are required for any production crawl.
When to use a unified API instead
For one-customer integrations where you have an iCIMS- customer relationship - apply for the iCIMS Partner Program. Get sponsored by the customer, complete the business review, and integrate with the per-customer Talent Cloud credentials.
For multi-tenant aggregation - iCIMS postings across many enterprise customers, for an aggregator, a sales- trigger workflow, or a hiring-signal intent product - JobsPipe indexes every public iCIMS careers site (both <company>.icims.com subdomains and customer-owned vanity domains), handles the module- version shape drift centrally, and serves the data alongside Workday, Greenhouse, Lever, BambooHR, and 30+ other sources in one normalized JSON schema. Free tier covers 5,000 requests/month with no partner application.
FAQ
Does iCIMS have a public jobs API?+
Not officially. The iCIMS Talent Cloud API at developer.icims.com is gated behind the iCIMS Partner Program - you have to apply, be approved, and (in most cases) be sponsored by an active iCIMS customer. There is no API key you can self-mint, no public sandbox, and no public OpenAPI spec. The closest 'public' surface is the internal JSON endpoint that <company>.icims.com careers sites use to render postings client-side - readable but undocumented and shape-sensitive to iCIMS module versions.
What is the iCIMS Talent Cloud API?+
iCIMS Talent Cloud is the suite of products iCIMS sells - Recruit (the ATS), Onboard (new-hire workflows), Connect (candidate CRM), and the Marketplace (partner integrations). The Talent Cloud API exposes records across these surfaces but is partner-gated. Most independent developers building a jobs aggregator are explicitly out of scope.
How do I get iCIMS API access?+
Apply to the iCIMS Partner Program at icims.com/partners. You will typically be asked to name an active iCIMS customer sponsoring your integration, complete a business review, and sign a partner agreement. Credentials are still per-customer-scoped after approval, which makes the program a fit for per-customer integrations rather than cross-tenant aggregation.
Where do iCIMS job postings actually live?+
On <company>.icims.com subdomains (the iCIMS-hosted pattern) or on customer-owned vanity domains like jobs.<company>.com that proxy iCIMS underneath. Many enterprise iCIMS customers - Siemens, PepsiCo, Lowe's, Verizon, Bayer, Nestle, ExxonMobil - run the vanity-domain pattern. Both patterns render postings client-side from an internal JSON endpoint.
Can I scrape iCIMS careers pages?+
Yes. The internal endpoint that careers sites use is reachable with a JSON fetch (cleaner than HTML scraping), but you'll need per-customer config, version-shape handling between iCIMS modules (Recruit vs Onboard vs Apply), and IP rotation under iCIMS' per-domain rate limits and CDN protection. The data is reachable; the maintenance is real.
How does JobsPipe handle iCIMS?+
JobsPipe indexes every public iCIMS careers site (both <company>.icims.com subdomains and customer-owned vanity domains running iCIMS embeds), tracks shape changes across iCIMS versions on our side, and normalizes everything into the same JSON schema we use for Workday, Greenhouse, and 30+ other ATSs. Free tier covers 5,000 requests/month with no credit card and no partner application.
What's the difference between iCIMS Recruit, Onboard, and Connect?+
iCIMS Talent Cloud is a suite. Recruit is the ATS (jobs, requisitions, candidates), Onboard handles new-hire workflows, Connect is the candidate-relationship/CRM surface, and the Marketplace surfaces partner integrations. From the outside, all of them surface jobs through the same <company>.icims.com careers site - which is what JobsPipe indexes. Internal/onboarding data is not visible to JobsPipe and not in scope.
Which iCIMS customers does JobsPipe cover?+
Every public iCIMS careers site. That includes Siemens, PepsiCo, Lowe's, Verizon, Bayer, Nestle, ExxonMobil, IBM (parts), and roughly 4,000 other public iCIMS customers as of 2026.
Does JobsPipe include candidate or applicant data from iCIMS?+
No. JobsPipe is jobs-only. Candidate, applicant, requisition-pipeline, and onboarding data are private per iCIMS customer and not accessible to JobsPipe at all.
Every public iCIMS careers site, one endpoint. No partner application required.
Get a free API key