US Transportation & Truck Driver Jobs API - JobsIndex by Aspen Tech Labs

Access US transportation and truck driver jobs through the JobsIndex API, built by Aspen Tech Labs. JobsIndex aggregates 6M+ active US job listings daily from 175K+ employer source sites, sourced directly from company career pages and ATS platforms, not scraped from job boards. The transportation job category covers 165,000+ active US job postings from 18,000+ unique employer domains, updated every day.

Sources include a mix of direct employers, logistics companies, freight carriers, fleet operators, and transportation providers, alongside recruitment agencies and staffing firms. This gives you full market coverage across both direct-hire and agency-sourced transportation roles.

This Actor covers the full breadth of US transportation and driving roles, well beyond truck drivers alone. Job subcategories include truck drivers, delivery drivers, bus drivers, taxi drivers, shuttle drivers, automotive technicians, mechanics, and owner-operators. Job titles span CDL-A and CDL-B truck drivers, OTR drivers, road drivers, tractor-trailer drivers, and more.

This Actor serves two primary use cases: teams that want to publish transportation job listings on their platform, and teams that need structured transportation workforce data for matching algorithms, AI model training, or logistics workforce intelligence.

What You Can Use It For

• Power a transportation job board, CDL jobs platform, or driver recruiting site with fresh job listings across all major US driving and transportation roles
• Feed a matching platform with structured transportation data, filterable by role, subcategory, location, salary, or posting age
• Monitor transportation hiring demand across US states, cities, and metro areas, useful for logistics workforce planning, market research, or sales intelligence
• Analyze advertised salary and seniority signals across truck driver, delivery driver, mechanic, and automotive technician roles by location
• Collect structured US transportation job postings for training datasets, research, or product development

Data Specs

Updated daily. Covers the full spectrum of US transportation and driving roles across all 50 states. Current dataset includes 165,000+ active job postings from 18,000+ unique employer domains. Sourced from employer career pages and ATS integrations, not aggregated from third-party job boards.

Built-In Search Preset

This Actor is fixed internally to country=United States and category=Transportation. The runtime always enforces those values even if different values are submitted. Users can narrow the search by transportation role, location, salary, company, posting age, employment type, remote status, or seniority.

Quick Start

{
  "what": "CDL-A truck driver",
  "region": "Texas",
  "size": 5
}

Input Parameters

Parameter	Description	Example
salary	Salary amount or range filter.	20h-30h
what	Main job search query. Supports keywords, boolean logic, exact phrases, and field-targeted search such as @title CDL-A driver or @(title,description) (owner operator).	CDL-A truck driver
where	Free-text location search. Supports place names, boolean logic, and field-targeted search such as @country United States or @(city,metro_area) (Dallas). Prefer structured location fields for exact filters.	Dallas
country	Fixed preset. Runtime always uses United States; changes are ignored.	United States
region	State, province, or region.	Texas
city	City filter.	Dallas
postal_code	Postal or ZIP code filter.	75201
metro_area	Metropolitan area filter.	Dallas-Fort Worth-Arlington, TX
title	Job title filter.	Truck Driver
company_name	Company name filter.	FedEx
company_domain	Company website domain.	fedex.com
category	Fixed preset. Runtime always uses Transportation; changes are ignored.	Transportation
sub_category	More specific transportation or driving role group.	Truck Driver
industry	Company industry filter.	Transportation and Warehousing
posted	Relative posting age or ISO date.	1w
employment_type	Employment type.	Full-Time
remote	Work arrangement filter. Supported values: remote, on-site, hybrid.	on-site
seniority	Seniority level.	Senior
page	Page number, starting from 0.	0
size	Number of results per page. Default 5, min 1, max 100.	5

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 = truck driver OR delivery driver
where = United States

Field-specific examples:

what = @title CDL-A driver OR OTR driver
where = @country United States

Multi-field examples:

what = @(title,description) (owner operator)
what = @(title,title_raw,description) (CDL-A OR CDL-B)
what = @(title,description) (tractor AND trailer)

where = @(country,region,city,metro_area,county,sub_city) (United States)
where = @(city,region,metro_area) (Dallas OR Texas)
where = @(city,region,metro_area) (Texas)

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 exposed for this Actor:

• region
• city
• postal_code
• metro_area

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

Limits and Pagination

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

Parameter	Default	Min	Max
page	0	0	Depends on size and the item cap
size	5	1	100

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:

Query shape	Max items	Effective max size	Over-size behavior
No company filter	1000	100	Validation error; not silently capped
Company filter plus another keyword or filter	20	20	Silent cap with capping metadata

A company filter means company_name, company_domain, or a company field referenced inside what. This Actor always applies the internal category=Transportation preset, so company-filtered requests use the company-plus-keywords cap.

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|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 available, where support advanced matching syntax but have safety limits:

Limit	Value	Error behavior
Raw URL length before decoding	700 characters	400 'what' or 'where' parameters exceed 700 characters
Decoded text length	500 characters	400 MATCH input exceeds length limit
Combined operator characters: ?, +, pipe, @	20	400 Too many MATCH operators
Unsafe SQL-like keywords	blocked	400 Unsafe MATCH expression

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.

Output

Each run stores job records in the default Apify dataset. The dataset schema includes an Overview table for the most useful fields and a Raw data (all fields) table for the complete JobsIndex record.

Example dataset item:

{
  "id": "3956505510037809027",
  "title": "CDL-A Truck Driver",
  "company_name": "Example Freight Company",
  "category": "Transportation",
  "sub_category": "Truck Driver",
  "country": "United States",
  "region": "Texas",
  "city": "Dallas",
  "salary_value": "28.00-35.00",
  "salary_currency": "USD",
  "salary_unit": "HOUR",
  "employment_type": "Full-Time",
  "remote": "on-site",
  "posted": "2026-04-20",
  "url_apply": "https://example.com/apply"
}

Field availability depends on the source job posting.

Custom Jobs Data

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