apify-isolved-jobs-apilisted

Scrape isolved jobs from any isolvedhire.com career site with the isolved Jobs API Actor (johnvc/isolved-jobs-api). Returns live job rows as JSON: title, hiring organization, tenant, employment type, locations with derived country, posted date, a sitemap last-modified stamp, apply URL, the employer's published salary when present, and the description as Markdown by default. Takes tenant slugs, tenant URLs, or single job URLs, and resolves legacy ApplicantPro sites too; filters by title, location, employment type, and salary before billing. updatedAfter turns a daily schedule into a real new-or-changed-postings feed using each job's own lastmod, checked before any page is fetched, so you pay only for what moved. Use when someone wants isolved jobs data, an isolved jobs api, to scrape isolved or ApplicantPro job postings for a job board or aggregator, isolved ATS listings, or change detection on isolved postings. Billed per job delivered with no start fee, and MCP-ready for Claude and other AI agents.
johnisanerd/claude-skill-isolved-jobs-api · ★ 0 · Data & Documents · score 78

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

# isolved Jobs, as Rows You Can Query Tenant slugs or job URLs in, live isolved jobs out as structured rows, each carrying the posting's own last-modified stamp so a scheduled run can return only what changed. ## When to use this skill - Someone wants isolved jobs and does not want to read isolvedhire.com career sites by hand. - You are filling a job board, a market-intel dashboard, or a sourcing tool with roles from isolved-hosted and ApplicantPro career pages. - You need a real change feed: isolved publishes a per-job last-modified stamp, so a daily run can return only new or edited postings with no state to keep. - You went looking for an isolved jobs API and found the vendor's product only, not a way to read the public postings as data. Not for: finding which employers run isolved in the first place. Use the companion `apify-companies-using-isolved` skill, built on the same Actor but shaped for tenant discovery. See `references/actor-index.md`. ## What you get One dataset row per job. `resultType` separates `job` rows from `error` rows. Core fields: - `id`, `url` (canonical, safe as a dedupe key), `applyUrl`, `title` - `organization`, `organizationUrl`, `tenant`, `tenantUrl` - `employmentType`, `locationsDerived`, `isRemote` - `datePosted`, `dateUpdated` (the sitemap last-modified stamp; date-granular) - `salaryRaw` (the employer's published pay, verbatim; usually null on isolved) - `descriptionMarkdown` (default add-on), `descriptionHtml`, `descriptionText` (opt-