Source · iCIMSiCIMS API.
The iCIMS Talent Cloud API is partner-only, and the public data lives in per-employer career portals. JobsPipe does not collect iCIMS. Here is what each surface gives you and how to reach the same employers.
JobsPipe does not collect iCIMS. The boards JobsPipe collects today are LinkedIn, Indeed, Y Combinator, Naukri, Workday, Greenhouse, Workable, SmartRecruiters, Ashby, Lever, Paylocity. A search with "source_or": ["icims"] returns no rows. This page explains what iCIMS exposes publicly and how to reach the same employers through the boards on the sources list.
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 apply, get approved (usually with a sponsoring iCIMS customer), and receive per-customer credentials. There is no API key you can self-mint, no public sandbox and no public OpenAPI spec.
What every iCIMS customer does have is a public careers site at careers-<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 whose shape varies by iCIMS module and release. JobsPipe does not collect that surface. iCIMS customers syndicate their postings to LinkedIn and Indeed through iCIMS's own distribution feeds, and JobsPipe does collect those boards.
Months of paperwork, usually requires a sponsoring iCIMS customer, and credentials are scoped to per-customer integrations, not aggregation across the iCIMS universe.
Each portal is reachable and renders from a JSON endpoint, but every employer is a separate config, the shape drifts between iCIMS modules and releases, and iCIMS rate-limits per domain behind CDN protection.
JobsPipe does not collect iCIMS. Search the same employers by name across the boards JobsPipe does collect; iCIMS customers distribute their postings to LinkedIn and Indeed, which JobsPipe carries as rows with the employer's name.
Does iCIMS have an API?
Yes, a partner-only one. The iCIMS Talent Cloud API exposes jobs, requisitions, candidates, applications, workflow statuses, onboarding tasks and CRM records through REST endpoints under a customer's own iCIMS instance, and it is reachable only with credentials issued through the Partner Program, which normally requires an iCIMS customer to sponsor you. There is no free public job feed the way Greenhouse, Lever or Ashby provide one. Every iCIMS customer does run a public career portal, careers-<company>.icims.com or a vanity domain, rendered from an internal JSON call. JobsPipe does not collect those portals; it collects the boards iCIMS distributes to.
Is the iCIMS API free?
No. There is no self-serve tier and no public pricing: API access is part of a partnership agreement, credentials are provisioned per customer instance, and iCIMS reviews each partner's business case. Reading the career portals directly costs nothing in fees but everything in maintenance: per-employer configs, module-dependent JSON shapes, per-domain rate limits and CDN abuse protection. JobsPipe's free tier returns 1,000 jobs a month across the boards it collects and the sandbox at POST /v1/sandbox/jobs/search needs no key, but neither returns iCIMS rows.
How do I get an iCIMS API key?
Through the Partner Program at icims.com/partners. You name a sponsoring iCIMS customer, complete a business review, sign a partner agreement, and iCIMS provisions credentials against that customer's instance: OAuth 2.0 client credentials for current tenants, HTTP Basic for older provisioning. A second customer means a second sponsorship. That fits a recruiting CRM or background-check vendor serving one employer; it does not fit reading postings across the iCIMS customer base. For that, create a JobsPipe key and query POST /v1/jobs/search with company_name_partial_match_or.
What does the iCIMS API documentation cover?
developer.icims.com sits behind partner credentials. Once inside it documents the Talent Cloud REST API by object (jobs, people, workflows, applications, onboarding, forms, lists), the authentication schemes, the Apply API for embedding application flows, iCIMS Connect for CRM workflows, the job-distribution feed formats iCIMS pushes to boards, webhooks and the Marketplace integration framework. It does not document a cross-customer read, because none exists. JobsPipe's docs at /docs cover the record shape returned for the boards JobsPipe does collect.
What JobsPipe returns for iCIMS
Nothing under "source_or": ["icims"]: JobsPipe does not collect iCIMS career portals. What JobsPipe returns is the same employers' postings where iCIMS distributes them: filter POST /v1/jobs/search with company_name_partial_match_or for the iCIMS customer you care about, and each record comes back with sources[0].provider naming the board it came from (for iCIMS customers most often linkedin or indeed), status, ghost_score, discovered_at, last_seen_at, seniority, and min_annual_salary_usd and max_annual_salary_usd when the posting states a range. The sample above shows the shape for one such record found on LinkedIn.
Vanity domains and iCIMS embeds
Many enterprise iCIMS customers prefer a vanity domain, jobs.<company>.com or careers.<company>.com, that proxies iCIMS underneath. From the outside it looks like a custom build; under the hood it hits the same internal endpoint with the same shape rules, and any direct iCIMS integration has to handle both URL patterns. iCIMS does not publish a customer list, so discovery is by inspecting careers pages for the iCIMS embed. That discovery-and-parsing layer, not the first fetch, is the real cost of building on iCIMS portals yourself.
Sample request
Filtering on "source_or": ["icims"] returns no rows because JobsPipe does not collect iCIMS. Employers that run iCIMS usually syndicate the same postings to LinkedIn and Indeed, which JobsPipe does collect, so filter by company instead and let sources[0].provider tell you which board each record came from.
curl https://api.jobspipe.dev/v1/jobs/search \
-H "Authorization: Bearer jp_live_your_key_here" \
-H "Content-Type: application/json" \
-d '{ "company_name_partial_match_or": ["acme"], "status": "active", "limit": 25 }'Every record is returned in the same JSON shape regardless of the board it came from. The full schema is documented in the docs.
Skip the scraper - try the API right now
Sample data from 30+ ATS feeds and job boards in the exact live JSON shape. No key needed.
Run the search to see normalized results.
{
"job_title_or": [
"software engineer"
],
"limit": 3,
"remote": true
}Live results are one free key away - same request against /v1/jobs/search.
Fields in every job record
FAQ
Does iCIMS have a public jobs API?+
Not officially. The Talent Cloud API at developer.icims.com is gated behind the Partner Program, with per-customer credentials and no self-mintable key. The closest public surface is the internal JSON endpoint that careers-<company>.icims.com portals use to render postings, which is readable but undocumented and shape-sensitive to iCIMS module versions.
Is the iCIMS API free?+
No. Access requires the Partner Program, which typically needs a sponsoring iCIMS customer, and even then credentials reach one customer. There is no free tier, no sandbox for outsiders and no public price. JobsPipe's free tier (1,000 jobs a month) covers the boards JobsPipe collects, which do not include iCIMS.
How do I get iCIMS API access?+
Apply to the iCIMS Partner Program at icims.com/partners, name an active iCIMS customer sponsoring your integration, complete a business review and sign a partner agreement. Credentials are OAuth 2.0 for newer customers and Basic auth for legacy tenants, scoped to that customer. For job postings across employers, use a JobsPipe key and search by company name.
Does JobsPipe collect iCIMS?+
No. "source_or": ["icims"] returns no rows. JobsPipe collects LinkedIn, Indeed, Y Combinator, Naukri, Workday, Greenhouse, Workable, SmartRecruiters, Ashby, Lever and Paylocity. Use company_name_partial_match_or to find an iCIMS customer's postings where they are syndicated.
What is 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, and the Marketplace surfaces partner integrations. From the outside all of them publish jobs through the same career portal, and none of them offers a public read API.
Where do iCIMS job postings actually live?+
On careers-<company>.icims.com subdomains or on customer-owned vanity domains like jobs.<company>.com that proxy iCIMS underneath, both rendered client-side from an internal JSON endpoint. iCIMS also pushes postings to LinkedIn, Indeed and Google for Jobs through its job-distribution feeds, which is how the same roles reach the boards JobsPipe collects.
Reach iCIMS employers through the boards JobsPipe collects - key in 30 seconds.
Get a free API key