Target Jobs API: retail floor and engineering hires in one table
One employer, two very different hiring programmes, returned in a single structured feed.
Unofficial. Not affiliated with, endorsed by, or sponsored by Target Brands, Inc., or by Workday, Inc. Structured facts only by default; no personal data is collected.
In plain language.
The useful thing about this employer’s vacancy list is that it contains two distinct hiring programmes that most analyses would separate, and seeing them together in one table changes what you notice.
In the run taken on 2 August 2026, ninety-three of a hundred requisitions were United States postings and seven were Indian. The Indian ones clustered in Bangalore; the American ones sat in stores, distribution sites and the Minneapolis head office.
Store-facing titles dominated the domestic side: Target Security Specialist, Human Resources Expert, Specialty Sales Team Leader, Beauty Team Leader. Alongside them sat a Seasonal Target Security Specialist, which is the kind of row that signals a hiring cycle turning.
An Apprentice – Retail Ops posting based in Bangalore sat in the same result set as those store roles. Without the country field these would be indistinguishable by title alone, and any purely title-based analysis would merge two separate labour markets.
Locations here are published as full street addresses rather than city names — 1000 Nicollet Mall in Minneapolis, 9501 Hudson Rd in Woodbury, 7000 Target Pkwy N in Brooklyn Park. Precise, but they need normalising before they will group cleanly by city.
Employment type was recorded as full-time on sixty-six of the hundred rows and left unstated on the remainder. An unstated value is returned as null rather than being filled in with an assumption, so seasonal and variable-hours roles are not silently miscounted.
Posting dates ran across four days at the end of July and the start of August, which suggests a board that turns over quickly. Weekly runs will show real movement rather than the same rows again.
A default run stops at a hundred rows to keep an exploratory run cheap. That limit is a single input away from being raised when you want the full picture.
Requisition identifiers are carried through from the source, so a follow-up run can report exactly which roles opened and which closed since the last one, including seasonal postings appearing and disappearing.
Output is JSON or CSV, with an optional white-label HTML hiring report generated from the same run.
Who it's for
- For retail talent teams. Seasonal postings appear in the same feed as permanent ones and are identifiable by title, so the start of a seasonal ramp is visible as it happens rather than in hindsight.
- For data and analytics engineers. Country and employment type are separate typed fields, which is what lets you split a mixed feed into domestic retail and offshore technology hiring in one query.
- For AI agents. Available over MCP with no required arguments. An agent can pull the current set, diff it against stored ids, and flag the appearance of seasonal roles without being told what to look for.
- For competitive and market researchers. The ratio of head-office to store to offshore postings, tracked over weeks, describes where a retailer is putting its money more honestly than a press release will.
Pricing
$1.50 per 1,000 jobs returned.
Charged once on the rows actually returned. A run that finds nothing costs only the start event.
What it does not do.
Only what is publicly advertised. Internal moves and unadvertised vacancies do not appear on a public careers site and cannot appear here.
Advert text is opt-in. The description body is the employer’s copyrighted writing. Structured facts come back by default and the prose only when you request it.
No individuals are collected. Nothing about recruiters, managers or candidates is gathered. The subject of every row is a vacancy.
Street addresses are not normalised. Locations are returned exactly as published. That preserves accuracy but means grouping by city is a step you perform, not one that has been done for you.
A blank employment type means unstated. Roughly a third of the sample carried no employment type. That is what the source published, and it is left null rather than defaulted to full-time.
Unofficial. Not affiliated with, endorsed by, or sponsored by Target Brands, Inc., or by Workday, Inc. Target is a trademark of its owner, used here only to identify whose public careers listings this tool reads. All rows originate from the employer’s own public careers site.
Fewer knobs. Better defaults.
Country as a real field
Domestic and offshore hiring can be separated without inspecting location strings.
Seasonal roles left intact
Titles are preserved verbatim, so a seasonal ramp is detectable in the data.
No configuration needed
The board is already set. The first run works without input.
Same tool, callable as an MCP server.
Target 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": 100, "country": "US" }