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
2 days ago
Last modified
Categories
Features
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.
Because the enforced country and category take precedence over where and what in the current JobsIndex API, those free-text inputs are intentionally not exposed. Use the structured job and location filters below to narrow results without replacing the preset.
Quick Start
{"title": "Warehouse Associate","region": "Texas","size": 5}
Input Parameters
| Parameter | Description | Example |
|---|---|---|
salary | Salary amount or range filter. | 20h-30h |
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
Location Filtering
This Actor is fixed to country=United States. Use structured location filters to narrow results within the US:
regioncitypostal_codemetro_area
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 |
Individual numeric bounds are checked before a run starts. Query-dependent pagination is checked after the run starts, as explained below.
One Run, One Page
Each run requests one page, not all available pages. size is the requested number of jobs for that page, with an absolute maximum of 100. Company filters can reduce the effective page size to 5 or 20; see Item Caps below.
For searches without company filters, the retrieval window is 1000 jobs: page * size must be less than 1000. The page number is zero-based.
size | Valid page range | First page outside the window |
|---|---|---|
| 100 | 0-9 | 10 |
| 20 | 0-49 | 50 |
| 10 | 0-99 | 100 |
| 1 | 0-999 | 1000 |
The last page can contain fewer jobs than requested. For example, page=12, size=80 starts at job 960 and can return up to 40 jobs. Narrow the search with filters to retrieve a different result set beyond the window; the Actor does not change the requested page or paginate automatically.
The input schema checks page and size individually. It cannot pre-validate their combination: page=10, size=100 passes the individual bounds but is rejected after a run starts, so the run can still finish as FAILED.
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 |
| Company filter only | 5 | 5 | Silent cap with capping metadata |
A company filter means company_name or company_domain. Another filter means a value in fields such as title, sub_category, industry, posted, salary, employment_type, remote, or seniority. The fixed country and category preset remains part of every request.
This Actor always applies the internal category=Warehouse preset, so company-filtered requests normally use the 20-item company|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"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.
Field Validation
Apify validates the input schema before creating a run, including requests made directly through the API. A schema violation returns HTTP 400 with error.type = invalid-input; no run is created. API clients should handle this response when starting the Actor; there is no run ID to poll or run error file to fetch.
| Input | Accepted values / limits |
|---|---|
page | Integer 0-999; the usable maximum also depends on size and query shape. |
size | Integer 1-100; company capping remains upstream. |
company_domain | A domain name only, e.g. example.com; 3-100 raw input characters. No protocol, path, port, or internal spaces. The API trims surrounding ASCII whitespace. |
posted | Recommended windows: 1d, 1w, 1m, 1y, or a real calendar date (YYYY, YYYY-MM, YYYY-MM-DD). Use 2-10 raw input characters. Surrounding ASCII whitespace is trimmed after the raw length check. Relative amounts use 1-4 digits without leading zeros. |
salary | 2-30 raw input characters. 1-9 digits plus h, d, w, m, or y; a range needs units on both ends, e.g. 20h-30h. Surrounding ASCII whitespace is trimmed. Decimals and currency prefixes are not accepted. |
employment_type | 2-50 raw input characters in total. Comma-separated values; 1-31 characters per item after trimming surrounding spaces. No empty items. |
seniority | 2-50 raw input characters in total. Comma-separated values; 1-31 characters per item after trimming surrounding spaces. No empty items. |
remote | remote, on-site, hybrid, or an empty string for no filter. |
| Other text fields | Raw input character ranges: region (2-80), city (2-100), postal_code (3-15), metro_area (2-100), title (2-200), company_name (2-150), sub_category (2-100), industry (2-100). Empty optional inputs remain allowed. |
Empty optional text fields are allowed and are omitted from the upstream request. Raw input length means the decoded string including surrounding whitespace, before API trimming, not URL-encoded bytes. The schema checks preliminary formats, list structure, and lengths, not whether a matching location, employer, role, or job exists. The API retains its detailed character checks, including permitted Unicode characters in list values. A valid search with no matching jobs succeeds with an empty dataset.
Query-dependent pagination, combined filters, and other backend-only checks remain upstream or runtime checks. If they reject a request after a run starts, the run can still finish as FAILED. Technical errors are not reported as successful searches.
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.