--- title: "iCIMS API" description: "iCIMS API: the partner-only Talent Cloud API, the public career portals where jobs are readable, and how to reach iCIMS employers' postings in one call." canonical: https://jobspipe.dev/sources/icims date_published: 2026-06-16 date_modified: 2026-09-26 author: Dvir Atias --- # iCIMS API iCIMS has an API, but a partner-only one: the Talent Cloud API exposes jobs, requisitions and candidates under a customer's own instance and is reachable only with Partner Program credentials, while the public career portals show the postings. JobsPipe does not collect iCIMS; the same employers' openings reach one search endpoint through the boards JobsPipe does collect, in one record shape across 30+ sources. [developer.icims.com](https://developer.icims.com/). > 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. **Canonical URL:** https://jobspipe.dev/sources/icims ## Coverage JobsPipe does not collect iCIMS. This page explains what iCIMS exposes publicly and how to reach the same postings where they are also published on a board JobsPipe does collect (Workday, Greenhouse, Lever, Ashby, LinkedIn, Indeed, SmartRecruiters, Workable, Personio, Recruitee, Teamtailor, EURES, Paylocity, Breezy HR, CV-Library, Y Combinator, Bayt, JobTech (Sweden), Resume-Library, Arbeitnow, Himalayas, Rise, Manatal, Pinpoint, JobScore, HireHive, The Muse, Remotive, Remote OK, Jobicy, Working Nomads, Landing.jobs). ## Why iCIMS jobs data is confusing 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-.icims.com or a vanity domain like jobs..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. ## Workarounds ### Apply for iCIMS Partner Program status Months of paperwork, usually requires a sponsoring iCIMS customer, and credentials are scoped to per-customer integrations, not aggregation across the iCIMS universe. ### Read careers-.icims.com portals 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. ### What JobsPipe offers instead 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. ## Fields available on every record - `id` - `job_title` - `company` - `company_domain` - `url` - `date_posted` - `discovered_at` - `last_seen_at` - `verified_at` - `status` - `closed_at` - `closed_reason` - `ghost_score` - `seniority` - `cities` - `state_code` - `min_annual_salary_usd` - `max_annual_salary_usd` - `technology_slugs` - `keyword_slugs` - `esco_skills` - `sources` ## FAQ ### How can I tell if a company uses iCIMS? Look at its careers site. iCIMS customers run portals at careers-.icims.com or on vanity domains like jobs..com that proxy iCIMS underneath, so inspect the careers page for the iCIMS embed. iCIMS publishes no customer list, which makes this per-site discovery the real cost of building on iCIMS portals yourself. ### Does the iCIMS API use OAuth or basic auth? Both, depending on the customer. Partner credentials are OAuth 2.0 client credentials for current tenants and HTTP Basic for older provisioning, and either way they are scoped to one customer's iCIMS instance. They are issued only through the Partner Program, so there is no self-minted key and a second customer means a second sponsorship. ### What is the difference between iCIMS Recruit, Onboard and Connect? iCIMS Talent Cloud is a suite. Recruit is the ATS for jobs, requisitions and 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. ### How do I find an iCIMS employer's jobs on LinkedIn or Indeed? iCIMS pushes customers' postings to LinkedIn, Indeed and Google for Jobs through its job-distribution feeds. JobsPipe does not collect iCIMS portals but does collect LinkedIn and Indeed, so filter POST /v1/jobs/search with company_name_partial_match_or for the employer. sources[0].provider on each record names the board it came from, most often linkedin or indeed for iCIMS customers. ## 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-.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 to start 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..com or careers..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. ## Related - **Product:** https://jobspipe.dev/jobs-api - **All sources:** https://jobspipe.dev/sources - **Docs:** https://docs.jobspipe.dev - **Sign up (free tier):** https://jobspipe.dev/signup --- Generated from structured data. View the rendered page at https://jobspipe.dev/sources/icims. --- Building this integration yourself? The steps above work. The alternative is one API over 30+ sources, already normalized and deduplicated. Try it right now - no key, no signup: ```bash curl -d '{"limit":3}' https://api.jobspipe.dev/v1/sandbox/jobs/search ``` Sample data, exact live schema. For live data get a free key (1,000 jobs to start) at https://jobspipe.dev/signup, then swap /v1/sandbox/jobs/search for /v1/jobs/search with an Authorization: Bearer header. Full agent index: https://jobspipe.dev/llms.txt?src=md-twin