apify-icims-jobs-apilisted

Pull live job postings from any iCIMS career site with the Apify iCIMS Careers API Actor (johnvc/icims-careers-api). iCIMS ships no public read API for postings, so this is the icims api most teams end up needing. Give it a career-site URL or just a company name and get structured rows back, each with title, the employer's own requisition id, organization, locations, employment type, posted and updated dates, salary when published, description as text or HTML or markdown, and the apply link. It covers both public iCIMS surfaces, the classic careers-tenant.icims.com portals and the modern iCIMS career sites hosted on the employer's own domain, and works out which one a company uses on its own. Use when the user wants iCIMS jobs, an ats api for recruiting or market data, job data for a board or aggregator, or to scrape job postings from a career site. Pay per job returned, MCP-ready for Claude and other AI agents.
johnisanerd/claude-skill-icims-jobs-api · ★ 0 · AI & Automation · score 66

Install: claude install-skill johnisanerd/claude-skill-icims-jobs-api

# iCIMS Jobs Without an Official API A career site in, structured requisitions out, on either of the two public iCIMS surfaces. ## When to use this skill - The user searched for iCIMS API documentation and found nothing they can sign up for. - They want live postings from employers they do not work for. - They are feeding a job board, a market-intel dashboard, or a recruiting tool. - They have a company name but not the career-site URL. Not for: monitoring the same employers on a schedule and reacting to changes. Use the companion apify-icims-job-monitor skill, which is far cheaper for that. See `references/actor-index.md`. ## Why there is no official option iCIMS sells integration access to its own customers. If the employer is not your employer, the public career site is the surface you have, and every one of those sites is laid out differently. This Actor normalizes both public layouts into one row shape, so a company that moves between them does not break your pipeline. ## What you get One dataset row per job. `result_type` separates `job` rows from `error` rows: - `url` (canonical and slug-free, safe as a dedupe key), `id` (the employer's own requisition number) - `title`, `organization`, `organization_url`, `category` - `description_text`, `description_html`, `description_markdown` - `employment_type`, `locations_derived`, `remote_derived`, `latitude`, `longitude` - `date_posted`, `date_updated`, `date_validthrough`, `salary_raw` - `apply_url`, `additional_fiel