Source · iCIMSiCIMS Jobs API.
The iCIMS Talent Cloud API is partner-only. JobsPipe covers every public iCIMS customer with no application form, no OAuth, and the same JSON shape as 30+ other ATSs.
Why people are confused about the iCIMS API
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 have to apply, be approved, and (in most cases) be sponsored by an active iCIMS customer. Most independent developers building a jobs aggregator are explicitly out of scope. There is no API key you can self-mint, no public sandbox, and no public swagger or 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 site renders job postings client-side from an internal JSON endpoint shaped like /jobs/intelliservices. The data is reachable, but the JSON shape varies by iCIMS module (Recruit, Onboard, Connect, Apply) and changes occasionally between iCIMS releases.
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.
Months of paperwork, usually requires a sponsoring iCIMS customer, and credentials are scoped to per-customer integrations - not aggregation across the iCIMS universe.
Possible but each customer is a separate scraper config, the underlying JSON endpoint changes between iCIMS releases, and iCIMS rate-limits per-domain on top of CDN-level protections.
Every public iCIMS customer, one endpoint, one key. No partner application, no OAuth, no per-customer scraper. Same JSON shape as Workday, Greenhouse, Lever, Indeed, and 30+ other sources. Free tier of 5,000 requests/month with no credit card.
iCIMS API documentation
iCIMS developer documentation lives at developer.icims.com and is gated behind active iCIMS Partner Program credentials. The major surfaces it covers, once you are in: the Talent Cloud REST API (jobs, candidates, requisitions, offers, all customer-scoped), iCIMS Connect for CRM workflows, the Apply API for embedded application flows, and the Marketplace integration framework for approved partners. None of these expose cross-customer reads. JobsPipe's documentation at /docs covers a normalized JSON schema we return for every public iCIMS careers site alongside 30+ other ATSs in the same shape.
iCIMS API key and authentication
iCIMS issues credentials per partner-customer pair through their Partner Program. Authentication is OAuth 2.0 for newer customers and HTTP Basic Auth for older tenants still on legacy provisioning. Each credential pair is scoped to one customer's Talent Cloud data only - no cross-tenant developer key exists. JobsPipe doesn't request iCIMS credentials. We consume only public iCIMS careers pages and authenticate every API call with one JobsPipe Bearer token.
iCIMS API access without Partner Program
There is no first-party path to iCIMS Talent Cloud API access outside the Partner Program. The closest thing is reading the public <company>.icims.com careers site (or the customer's vanity domain) directly - that surface is reachable without iCIMS credentials but is undocumented, shape-sensitive, and rate-limited per-domain. JobsPipe consumes that surface on your behalf across every public iCIMS customer, handles version differences, and serves a stable schema. No iCIMS partnership needed on the JobsPipe consumer side.
iCIMS API integration
Single-customer iCIMS integration (sync candidates to your CRM, push jobs from your HRIS, react to requisition status changes) requires Talent Cloud API credentials that customer mints through the Partner Program flow. Cross-customer integration - reading jobs across many iCIMS-using companies into one feed - is JobsPipe: every public iCIMS customer indexed every 24 hours, served in the same JSON schema as Workday, Greenhouse, Lever, Indeed, and 30+ other sources, through one endpoint with one key.
iCIMS API alternatives
Alternatives for cross-customer iCIMS jobs data: (1) Apply for and operate the Partner Program for each customer you want to cover - months of paperwork and per-customer credentials. (2) Scrape <company>.icims.com subdomains directly and maintain version-shape adapters yourself - works for ten customers, breaks at a hundred. (3) Use JobsPipe, which already covers every public iCIMS customer with normalization, freshness, and the same JSON shape as 30+ other sources. Free tier of 5,000 requests/month with no credit card.
Companies using iCIMS
iCIMS is the ATS of choice for enterprise and Fortune-500-adjacent organizations - industrial (Siemens, Bayer, ExxonMobil), CPG (PepsiCo, Nestle), retail (Lowe's), telecom (Verizon), and a long tail of mid-to-large customers. JobsPipe's iCIMS coverage spans every public iCIMS careers site, so the live customer list is implicit in any /v1/jobs?source=icims response - the unique tenant values are the universe.
Sample request
curl "https://api.jobspipe.dev/v1/jobs?source=icims" \
-H "Authorization: Bearer $JOBSPIPE_KEY" \
-H "Accept: application/json"Sample response
{
"id": "ic_MWE3NWM5YTctMGJmNw",
"source": "icims",
"tenant": "siemens",
"title": "Power Electronics Engineer",
"company": "Siemens",
"location": {
"city": "Princeton",
"region": "NJ",
"country": "US",
"remote": false
},
"salary": {
"min": 115000,
"max": 145000,
"currency": "USD",
"period": "year",
"source": "explicit"
},
"employment_type": "full_time",
"posted_at": "2026-05-10T13:24:00Z",
"expires_at": null,
"apply_url": "https://jobs.siemens.com/jobs/...",
"description": "Siemens is hiring a Power Electronics Engineer for our grid technologies group, working across HVDC and renewable-integration projects ..."
}Every iCIMS job record is returned in the same JSON shape as every other JobsPipe source. The full schema is documented in the docs.
Fields in every iCIMS job record
FAQ
Is the iCIMS API free?+
No. The iCIMS Talent Cloud API is partner-gated - you cannot get credentials without the Partner Program, and the program typically requires a sponsoring iCIMS customer. JobsPipe is free at the 5,000 requests/month tier (no credit card) and covers every public iCIMS customer through one endpoint, which is usually what teams searching 'free iCIMS API' actually need.
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. JobsPipe avoids the partner path entirely - we consume only public iCIMS careers data and authenticate with one JobsPipe key.
Does iCIMS have a public Jobs API?+
Not officially. The Talent Cloud API requires partner credentials. 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. JobsPipe consumes that internal surface across every public iCIMS customer and serves a stable normalized JSON schema instead.
How do I scrape iCIMS careers pages?+
Each <company>.icims.com (or customer vanity domain) renders jobs from an internal JSON endpoint - readable with a JSON fetch rather than HTML scraping. You will still need: per-customer config, version-shape handling between iCIMS modules (Recruit vs Onboard vs Apply), and IP rotation under iCIMS' per-domain rate limits. JobsPipe handles all three on our side.
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.
What about iCIMS customers with vanity domains?+
Many iCIMS customers run a vanity domain like jobs.<company>.com that proxies iCIMS underneath. JobsPipe follows both patterns - <company>.icims.com subdomains and customer-owned vanity domains running iCIMS embeds - and serves them under the same source=icims namespace.
Can I filter iCIMS jobs by department, location, or category?+
Yes. ?tenant=<customer-slug> for one iCIMS customer, ?country=US for country, ?region=NJ for state, ?department=engineering for department. Full filter list is in our docs.
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.
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.
Try iCIMS data free - 5,000 requests/month, no credit card.
Get a free API key