US Warehouse Jobs API
Pricing
from $1.20 / 1,000 job records
US Warehouse Jobs API
Find US warehouse job postings by role, location, company, salary, posting age, employment type, remote status, and seniority. Built for warehouse job boards, recruiting products, and workforce intelligence.
Pricing
from $1.20 / 1,000 job records
Rating
0.0
(0)
Developer
Aspen Technology Labs, Inc.
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
a day ago
Last modified
Categories
Share
US Warehouse Jobs API - JobsIndex by Aspen Tech Labs
Access 120,000+ active US warehouse jobs from 15,500+ unique employer domains through the JobsIndex API, updated every day.
The warehouse job category is one of the most in-demand job categories in the US, spanning everything from warehouse workers and material handlers to supply chain specialists, logistics managers, and distribution supervisors.
Data comes directly from employer career sites and ATS platforms across the US. The dataset includes a mix of direct employers and recruitment agencies, so you get a broad view of who is actually hiring, not a filtered slice of the market.
What Is In The Dataset
The warehouse job category breaks down into subcategories including warehouse workers, supply chain, and logistics management. Within those, job titles span the full operational stack:
- Warehouse operations: warehouse associate, material handler, loader, package handler, yard person
- Logistics and distribution: logistics specialist, distribution supervisor, supply chain specialist
- Management: logistics manager, warehouse manager, supply chain manager
All results are filterable by location, salary, posting date, company, employment type, remote status, seniority, and more.
What You Can Use It For
- Power warehouse, logistics, distribution, or supply chain job boards with fresh listings from employer career sites and ATS platforms
- Feed matching platforms, staffing tools, and recruiting workflows with structured warehouse jobs data
- Monitor warehouse hiring demand across US states, cities, metro areas, employers, and role types
- Analyze advertised salary, seniority, and posting signals across warehouse operations, logistics, and supply chain roles
- Collect structured warehouse jobs for labor market intelligence, model training, supply chain workforce research, or product development
Built-In Search Preset
This Actor is fixed internally to country=United States and category=Warehouse. The runtime always enforces those values even if different values are submitted. Users can narrow the search by warehouse role, location, salary, company, posting age, employment type, remote status, or seniority.
Quick Start
{"what": "warehouse associate","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 warehouse associate or @(title,description) (material handler). | warehouse associate |
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. | Warehouse Associate |
company_name | Company name filter. | Amazon |
company_domain | Company website domain. | amazon.com |
category | Fixed preset. Runtime always uses Warehouse; changes are ignored. | Warehouse |
sub_category | More specific warehouse, supply chain, or logistics role group. | Warehouse Worker |
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. | Manager |
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 hourd- per dayw- per weekm- per monthy- per year
Examples:
20h-30h- hourly rate between 20 and 3035h- fixed hourly rate20h-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 = warehouse associate OR material handlerwhere = United States
Field-specific examples:
what = @title warehouse associate OR material handlerwhere = @country United States
Multi-field examples:
what = @(title,description) (forklift)what = @(title,title_raw,description) (warehouse OR logistics)what = @(title,description) (supply AND chain)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,referencecategory,sub_category,seniority,industry,company_typecompany_name,company_domain,company_name_rawemployment_type,remote,languageposted,posted_raw,expiredurl_source,url_applysalary_value,salary_currency,salary_unitid
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:
regioncitypostal_codemetro_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=Warehouse 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 requestedsizesize_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": "Warehouse Associate","company_name": "Example Distribution Company","category": "Warehouse","sub_category": "Warehouse Worker","country": "United States","region": "Texas","city": "Dallas","salary_value": "20.00-25.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 Warehouse 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.