Jobvite Jobs Scraper
Pricing
from $2.99 / 1,000 jobvite career roles
Jobvite Jobs Scraper
Scrape public Jobvite-hosted company career sites into structured job records with descriptions, salary when published, job IDs, locations, employment type, and apply links.
Pricing
from $2.99 / 1,000 jobvite career roles
Rating
0.0
(0)
Developer
Jobs API
Maintained by CommunityActor stats
0
Bookmarked
3
Total users
2
Monthly active users
16 days ago
Last modified
Categories
Features
Share
Jobvite Jobs Search Scraper
This Actor reads ordinary public listings and job details hosted on Jobvite career sites. It does not sign in, submit applications, read candidate data, use cookies, or alter browser/network fingerprints. The default board is Reveal Careers.
The Actor requests board and detail pages sequentially, with a minimum 250 ms gap. If an ordinary public request receives HTTP 401, 403, 429, or 451, or a visible source-authored access-denial/CAPTCHA/security challenge, it stops immediately, discards buffered job rows, and records resultStatus: SKIPPED, the diagnostic, and request receipts in the key-value store. It does not retry a blocked request, switch identities/routes/browsers, or solve challenges. A generic transport failure or proxy-auth response is recorded as DEFERRED, not treated as proof the site blocked access.
status and runStatus describe the Apify platform outcome (SUCCEEDED or FAILED); resultStatus describes the data outcome (COMPLETE, LIMITED, SKIPPED, DEFERRED, NO_DATA, or FAILED). A confirmed source barrier is a successfully handled run, so the platform status remains SUCCEEDED while the result is SKIPPED. Fatal zero-row processing failures use FAILED and call Actor.fail. If later processing or persistence fails after dataset writes succeeded, those rows remain stored and the result is LIMITED.
Modes and inputs
Search a public board and enrich results from their detail pages:
{"mode": "search","companySlugs": ["reveal"],"maxItems": 2,"includeDetails": true,"maxRequests": 20,"requestDelayMs": 1000}
Fetch one page verified in Chrome, Director, Customer Success:
{"mode": "single","jobUrl": "https://jobs.jobvite.com/reveal/job/o9BrAfwv"}
For several explicit public details, use mode: "multiple" and jobUrls as objects such as { "url": "https://jobs.jobvite.com/reveal/job/o9BrAfwv" }. The jobUrl alias accepts one URL string. Search mode accepts listing URLs and company slugs, not detail URLs. Single mode requires exactly one valid Jobvite detail URL; multiple mode requires at least one. Unknown fields are rejected. In particular, there are no public userAgent or concurrency controls.
query, locations, and categories are case-insensitive filters. includeDetails defaults to true; set it to false only when listing links are sufficient. maxItems limits emitted records, and maxRequests caps explicit page-fetch attempts, including transient retries. Fetch automatically follows redirects, so redirect hops may add network requests outside this cap and are not receipted individually. The Actor retries only HTTP 408, 425, and 5xx responses; it does not retry proxy-auth responses or transport exceptions. Developer options are bounded: requestDelayMs (250–5000; default 500), maxRetries (0–4; default 2 for those transient HTTP responses), timeoutMs (5–120 seconds), maxResponseBytes (100 KB–50 MB), and maxDescriptionChars (1,000–500,000). HTTP 401, 403, 429, 451 and visible source-authored challenges are never retried.
Dataset fields
Detail records use public JobPosting JSON-LD and visible page markup when present. Extracted facts include the stable job ID, title, company and published organization details, category, structured location parts, employment/workplace type, full description and sectioned responsibilities/requirements/benefits, keywords, published salary, application link, dates, public media, and page title/description. Fields absent from a particular public posting are omitted, not fabricated. Each emitted posting reports dataQuality.meaningfulSourceFieldCount; only detail-enriched job-posting records with at least 21 distinct meaningful source facts are emitted. Listing-only links, summary rows, and diagnostics never enter the dataset. Request receipts belong in the REQUEST_RECEIPTS key-value record (also summarized as sourceCalls); diagnostics belong in RUN_DIAGNOSTICS.
Run evidence is written to OUTPUT and OUTPUT_SUMMARY; access/request diagnostics are in RUN_DIAGNOSTICS, request receipts are in REQUEST_RECEIPTS, the source policy is in SOURCE_METADATA, and health information is in RUN_HEALTH. Setting includeDetails: false prevents detail verification, so no listing-only rows are emitted and the result is DEFERRED. Application URLs are reported but never followed or submitted.
Local development
npm cinpm testnpm run checkapify validate-schema
The checked-in INPUT.json, INPUT-single.json, and INPUT-multiple.json are bounded public examples. For each local run, choose a new actor-relative storage directory that does not already exist; never reuse an existing dataset directory or use --purge:
Test-Path .\storage-jobvite-run-01$env:APIFY_LOCAL_STORAGE_DIR = 'storage-jobvite-run-01'apify run --resurrect --input-file .\INPUT.jsonnpm run validate -- .\storage-jobvite-run-01
If Test-Path reports True, choose a different fresh relative directory before running. Local results do not qualify or imply an Apify Cloud run; this repository has not been Cloud-qualified.
This independent Actor is not affiliated with Jobvite or Reveal. Use it only for public job information and in accordance with the source site's terms and applicable law.