Ashby Jobs API

An actor that provides programmatic access to a pre-scraped and enriched database of job listings from career sites using the Ashby ATS. It's designed for job boards needing reliable backfill with high-quality data.

Overview

This actor is not a live scraper you run. Instead, it queries a centralized database that we maintain. Our systems continuously scrape thousands of company career sites using Ashby. Jobs are added to the database twice per hour after enrichment, and expired jobs are purged daily. You access this curated dataset via the API.

Note: There's a limit of 5,000 jobs per run. Contact us if you need more.

Looking for jobs from multiple ATS? Check out our Career Site Job Listing API.

Key Features

• Pre-Scraped Database: Pulls from a database containing jobs posted in the last 6 months from Ashby-hosted career sites.
• Continuous Updates: New jobs are added twice per hour; expired jobs are removed daily.
• AI Enrichment (BETA):
  • Job Details: Uses an LLM to extract key details (e.g., salary, experience level) from descriptions. Covers >99.9% of jobs. Note: This is a one-shot prompt, so minor errors are possible.
  • LinkedIn Company Data: Maps jobs to LinkedIn company profiles, adding data like employee count and industry. Accuracy is ~99%, covering >95% of jobs.
• Domain Derivation: Identifies the company's domain/homepage (~98% accuracy) when not provided by the ATS.
• Change Detection (In Progress): Systems are being built to detect when posted jobs are modified. For some ATS, changes are already flagged via date_modified and modified_fields fields.
• Deduplication Note: Jobs are unique by URL in the database. However, companies sometimes create duplicates or list the same role for multiple locations. For a clean dataset, consider deduplicating further by title + organization or title + organization + locations.

How to Use

Configure and run the actor on Apify. The main input is typically a search query or filter parameters to target specific jobs from the database.

To retrieve results as XML from a scheduled run:
1. Create a saved task: https://docs.apify.com/platform/actors/running/tasks
2. Create a schedule for that task: https://docs.apify.com/platform/schedules
3. Use the following endpoint, replacing {task-id} and {apiKey}:
https://api.apify.com/v2/actor-tasks/{task-id}/runs/last/dataset/items?token={apiKey}&format=xml
* {task-id} is the last string of characters in your task's URL.
* {apiKey} is your Apify API key (Settings > API & Integrations).

Input / Output

Input: Configuration parameters for filtering the job database (e.g., keywords, date ranges, locations).

Output: A dataset of job objects. Each job includes standard listing data (title, description, URL, location, etc.) plus enriched fields where available:
* llm_extracted_details (BETA)
* linkedin_company_data (BETA)
* derived_domain
* date_modified & modified_fields (if changes detected)

FAQ

• Is this a scraper? Technically, yes—but in the backend. You access our pre-scraped database, which is more reliable and allows for pre-enrichment.
• Can I retrieve only new jobs? Use our Career Site Job Listing API for that functionality.
• Can I see a job count before running? Not currently. Test with the free plan or create an issue with your parameters for assistance.

Feedback? Please leave a review if you find it useful. For issues or to request a missing organization, create an issue here.