Lowe's Jobs API: store-level vacancies, shift by shift
Hourly retail hiring at store level, returned as data you can group, count and compare between weeks.
Unofficial. Not affiliated with, endorsed by, or sponsored by Lowe’s Companies, Inc., or by Workday, Inc. Structured facts only by default; no personal data is collected.
In plain language.
Most hiring feeds are built around salaried roles and treat hourly work as an afterthought. This one is pointed at an employer whose advertised vacancies are overwhelmingly hourly, and it keeps the detail that makes hourly hiring legible.
The clearest signal in the run of 2 August 2026 was the employment split. Of the hundred requisitions returned, sixty-nine were full-time and thirty-one part-time. Part-time was not a rounding error here; it was almost a third of everything advertised.
Shift information is embedded in the titles this employer publishes, and it survives into the data unaltered. Full Time – Receiver/Stocker – Day and Part Time – Loader/Cart Associate – Flexible are single strings that already tell you the contract type and the working pattern.
The rest of the sample read like a store roster: fulfilment associates, merchandising service associates, sales associates. This is the operational core of a large-format retailer, and it is exactly the population that is hardest to observe from the outside.
Locations are individual stores, each carrying its own number. Mount Airy 0478, Alcoa in Blount County 0638, north Jacksonville 2472, Iwilei in Honolulu 2336. That numbering makes it possible to follow one shop over time instead of aggregating a whole metro.
Ninety-nine of the hundred rows were United States postings, with a single Indian one in the sample — a reminder that even a domestic retailer has some presence elsewhere, and that filtering by country is worth doing explicitly.
Posted dates spanned only the last three days of the window, which fits a business advertising hourly roles continuously rather than in campaigns. Frequent runs therefore surface genuine movement.
The hundred-row ceiling on a default run is a cost control. For store-level work you will often want it higher, and it is a single input away.
Second and subsequent runs can be handed the requisition ids you already hold, and will answer with what is new and what has closed rather than repeating themselves.
Everything comes back as JSON or CSV, with an optional white-label HTML report from the same run for stakeholders who want a document rather than a dataset.
Who it's for
- For staffing agencies and local recruiters. Store numbers make it obvious which specific shops are hiring and for which shifts, so outreach can be aimed at a location rather than a region.
- For automation and data teams. A stable schema with contract type as its own field, so full-time and part-time volumes can be counted separately without parsing job titles by hand.
- For AI agents. Exposed as an MCP tool that runs with no arguments. An agent can pull the current set, compare it against last week’s ids and report only the part-time roles that appeared.
- For labour-market and retail researchers. The full-time to part-time ratio in a live vacancy list is a direct read on how a retailer is structuring its workforce right now.
Pricing
$1.50 per 1,000 jobs returned.
One charge, taken from the final set of rows. An empty result costs nothing beyond the start event.
What it does not do.
Advertised roles only. Vacancies filled by internal transfer or through an agency never reach the public careers site, so they are not here either.
Descriptions stay off by default. Advert copy is the employer’s intellectual property. Facts are returned as standard; the body text is an explicit opt-in.
No personal data. Store managers, recruiters and applicants are never part of the output. Only the vacancy is described.
Shift detail comes from the title, not a separate field. Day, Opening and Flexible are how this employer writes its titles. They are preserved verbatim rather than parsed into a schedule field that would invent structure the source does not publish.
Pay is not published here. The salary field stayed empty across the sample. Where an employer does not publish a rate, no rate is inferred.
Unofficial. Not affiliated with, endorsed by, or sponsored by Lowe’s Companies, Inc., or by Workday, Inc. Lowe’s is a trademark of its owner, used here only to identify whose public careers listings this tool reads. Data is read from the employer’s own public careers site.
Fewer knobs. Better defaults.
Part-time visible as data
Contract type is its own field, so hourly hiring can be counted rather than estimated.
Store-level granularity
Each row keeps the individual store identifier the source published.
Nothing to configure
The board is preset. The first run needs no input at all.
Same tool, callable as an MCP server.
Lowe's Jobs API runs on Apify, which means it's exposed as a remote MCP tool with no extra setup. Point any MCP-compatible agent (Claude, Cursor, and others) at the endpoint below.
View full API reference on Apify{ "maxJobs": 500, "employmentType": "part-time" }