Pricing

Rating

Developer

Actor stats

Categories

Share

JobsIndex API - JobsIndex by Aspen Tech Labs

Access fresh, deduplicated job postings from direct employer career sites worldwide through the JobsIndex API, built by Aspen Tech Labs. JobsIndex aggregates 11M+ active job postings daily from 300K+ employer source sites globally. Job data is sourced directly from company career pages and ATS platforms, not scraped from job boards or aggregators.

Use this Actor when you need flexible access to the full JobsIndex jobs API rather than a pre-filtered specialty Actor. You can search by keyword, title, company, location, category, salary, seniority, employment type, work arrangement, posting age, and more.

What You Can Use It For

• Power job boards, job search features, or backfill workflows with fresh job postings
• Find jobs by title, keyword, company, location, category, industry, or posting age
• Monitor hiring activity for specific companies or employer domains
• Build recruiting, HR analytics, sales intelligence, workforce intelligence, or labor-market products
• Retrieve structured job data with company, location, salary, category, seniority, remote status, source URL, and application URL fields where available

Why JobsIndex Is Different

• 11M+ active job postings worldwide
• 300K+ employer source sites
• Direct employer career-site and ATS coverage
• Fresh active jobs, updated daily
• Deduplicated job records
• Direct source and application links where available
• Salary, location, company, category, seniority, remote, and employment-type fields where available
• Historical job postings, custom feeds, and bulk delivery available separately

Quick Start

Fresh software jobs in the United States

{
"what":"software engineer",
"country":"United States",
"posted":"1w",
"size":10
}

Jobs for a specific company domain

{
"company_domain":"ibm.com",
"size":10
}

Jobs with salary data

{
"country":"United States",
"salary":"20h-30h",
"size":10
}

Remote jobs

{
"remote":"remote",
"what":"customer success",
"size":10
}

Input Parameters

Salary Filter Format

Use:

NUMBER[UNIT]

or:

NUMBER[UNIT]-NUMBER[UNIT]

Supported units:

• h - per hour
• d - per day
• w - per week
• m - per month
• y - per year

Examples:

• 20h-30h - hourly rate between 20 and 30
• 35h - fixed hourly rate
• 20h-200000y - range from hourly to yearly comparison

Advanced Filters

what and where support plain-text search, boolean logic, and field-targeted search.

If no field is provided, the API expands the search across a default set of relevant fields.

Plain keyword examples:

what = engineer OR manager
where = United States

Field-specific examples:

what = @title engineer OR manager
where = @country United States

Multi-field examples:

what = @(title,description) (python)
what = @(title,title_raw,description) (engineer OR manager)
what = @(title,description) (python AND developer)
where = @(country,region,city,metro_area,county,sub_city) (United States)
where = @(city,region,metro_area) (San Francisco OR California)
where = @(city,region,metro_area) (California)

When using where, avoid sending separate structured location parameters for the same request unless you want those structured parameters to take priority. For example, country, region, city, postal_code, and metro_area can override or narrow where.

Common job/content fields for what:

• title, title_raw, description, reference
• category, sub_category, seniority, industry, company_type
• company_name, company_domain, company_name_raw
• employment_type, remote, language
• posted, posted_raw, expired
• url_source, url_apply
• salary_value, salary_currency, salary_unit
• id

Common location fields for where:

• country, region, city, metro_area, county, sub_city, postal_code

Location Filtering

For precise location matching, use structured filters when possible:

• country
• region
• city
• postal_code
• metro_area

Use where as a free-text location search when structured location filters are not set. If where is provided together with structured location filters, the structured filters take priority and where may be ignored or narrowed.

Limits and Pagination

This Actor uses the JobsIndex jobs API. Results are paginated with page and size.

Invalid page or size values can return 400 Invalid page or size parameters.

Item Caps

The maximum number of retrievable jobs depends on the query shape:

A company filter means company_name, company_domain, or a company field referenced inside what. Another keyword or filter means anything in what other than company_*, or a value in fields such as title, category, sub_category, industry, posted, salary, employment_type, remote, or seniority.

When a company-filtered request asks for size greater than the effective cap, the API returns up to the capped number of results instead of erroring. The response metadata includes:

• size_requested - the original requested size
• size_capped_by - "company" for the 5-item cap or "company|keywords" for the 20-item cap

On uncapped responses, size_requested and size_capped_by are not present.

No-company-filter requests are not silently capped. If the request exceeds the 1000-item retrieval window, the API can return 400 Item limit reached. Maximum of 1000 items can be retrieved.

Free-Text Query Limits

what and where support advanced matching syntax but have safety limits:

Unsupported characters may be normalized before search. Unbalanced quotes and trailing @ characters may be stripped.

Field Validation

Invalid filter values can return 400 Invalid value for parameter: <name>. Common validation examples include malformed company domains, invalid dates or relative posted values, invalid salary format, invalid job IDs, unsupported location formats, or overly long field values.

ID Lookup Shortcut

When id is provided, the search query is bypassed and the API returns the matching job record or records. Job IDs must be numeric; otherwise the API returns 400 Invalid job id format.

Output

Each run stores job records returned by the JobsIndex API in the default Apify dataset and metadata in meta.json in the default key-value store.

The dataset schema exposes the raw JobsIndex job fields returned by the API. Common fields include:

• id
• title, title_raw
• category, sub_category, seniority
• reference, industry, company_type
• company_name, company_name_raw, company_domain
• posted, posted_raw, expired
• url_source, url_apply
• country, region, city, metro_area, county, sub_city, postal_code
• salary_value, salary_currency, salary_unit
• employment_type, remote, language
• description

meta.json includes:

• page
• size
• total
• pages
• returned_count
• query
• status_code
• size_requested and size_capped_by, when company-filter capping is applied

Example dataset item:

{
"id":"3956505510037809027",
"title":"Software Engineer",
"company_name":"Example Company",
"category":"Information Technology",
"sub_category":"Software Development",
"country":"United States",
"region":"California",
"city":"San Francisco",
"salary_value":"120000.00-160000.00",
"salary_currency":"USD",
"salary_unit":"YEAR",
"employment_type":"Full-Time",
"remote":"hybrid",
"posted":"2026-04-20",
"url_apply":"https://example.com/apply"
}

Field availability depends on the source job posting. Missing or unavailable values may appear as an empty string, "n/a", or null, depending on the field and source data.

Empty Results

If no jobs match your query, the API returns a successful response with total: 0 and an empty data array. The Actor run still succeeds and writes an empty dataset plus metadata.

Custom Jobs Data

For custom job data needs, bulk downloads, or tailored job feeds, contact us via JobsIndex or by email. You can also explore JobMarketPulse, our next-generation labor and job market intelligence platform.