Amazon hiring-trend tracking
Use Amazon Jobs endpoints to turn amazon hiring-trend tracking into repeatable API requests with documented inputs and JSON responses.
Search Amazon's own careers site (amazon.jobs) — by keyword, Amazon's job-category taxonomy, or country — and get a single posting by id, as structured JSON. No login, no per-category scraper to maintain.
Search Amazon's own careers site (amazon.jobs) by keyword, category, or country and get one posting by id, as structured JSON.
Endpoint families
2
Documented params
9
Examples
2
Live catalog snapshot
Active endpoints
2
Methods
GET
Required params
3
Schema refs
2
{
"platform": "Amazon Jobs",
"endpoint": "amazon-jobs-search",
"method": "GET",
"path": "/amazon-jobs/search",
"auth": "apiKey"
}Use cases
Search Amazon's own careers site (amazon.jobs) by keyword, category, or country and get one posting by id, as structured JSON.
Use Amazon Jobs endpoints to turn amazon hiring-trend tracking into repeatable API requests with documented inputs and JSON responses.
Use Amazon Jobs endpoints to turn job posting aggregation and monitoring into repeatable API requests with documented inputs and JSON responses.
Use Amazon Jobs endpoints to turn recruiting and talent-market research into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live Amazon Jobs endpoint catalog — 2 endpoints, 9 documented request parameters, and 2 published response schemas — the same catalog Docs and Playground run against.
2 documented Amazon Jobs endpoints, grouped into 2 request families — Job and Search.
9 request parameters are documented across those Amazon Jobs endpoints, 3 of them required — the full input contract is public before you write any integration code.
2 of the 2 Amazon Jobs endpoints ship a recorded example response, and 2 carry a documented response schema — you can code against the real JSON before the first request.
Amazon Jobs endpoints document their error responses (400, 404, 429 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
2 hosted MCP tools back the Amazon Jobs endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
These cards are generated from the active endpoint catalog, so the landing page reflects the same API surface used by Docs and Playground.
/amazon-jobs/job
/amazon-jobs/search
Endpoint catalog
/amazon-jobs/searchSearches Amazon's public careers site (amazon.jobs) via its credential-free search JSON. Each result includes the full description and qualifications inline. `sort` accepts `relevant` (default, upstream relevance ranking) or `recent` (newest posted first). Either `q` or `category` (or both) must be given -- `category` filters by Amazon's own job-category taxonomy and works with no text query at all.
Response notes
- A valid query with no matches returns `total: 0` and an empty `jobs` array (not an error). This includes `category=fulfillment-center-warehouse-associate`, which returns zero results live — Amazon's hourly fulfillment-center hiring appears to run through a separate system, not this search API. - `jobs[].description`, `basic_qualifications`, and `preferred_qualifications` are HTML-stripped plain text. - `jobs[].posted_at` is best-effort parsed to RFC3339 from Amazon's free-text posted date; it is omitted if the upstream format ever drifts. - Invalid `category`, `limit` (over 100), or `sort` values return an invalid-parameter error before upstream IO. - State/city-level location filtering is not exposed — Amazon's `search.json` did not honor it reliably during research; only the country filter was confirmed working. Example response: ```json { "code": 200, "msg": "OK", "data": { "query": "software engineer", "country": "USA", "page": 1, "limit": 20, "total": 2027, "jobs": [ { "id": "10386857", "title": "Software Engineer", "company": "Amazon Web Services Australia Pty Ltd", "location": "Sydney, New South Wales, AUS", "city": "Sydney", "state": "NSW", "country": "AUS", "category": "Software Development", "schedule_type": "full-time", "posted_at": "2026-04-09T00:00:00Z", "description": "AWS Infrastructure Services owns the design, planning, delivery, and operation of all AWS global infrastructure...", "basic_qualifications": "Bachelor's degree in Computer Science or other technical degree or related experience...", "preferred_qualifications": "Experience building complex software systems that have been successfully delivered to customers...", "url": "https://www.amazon.jobs/en/jobs/10386857/software-engineer", "apply_url": "https://account.amazon.com/jobs/10386857/apply" } ], "source_url": "https://www.amazon.jobs/en/search.json?base_query=software+engineer&limit=20&offset=0&result_limit=20" } } ```
MCP tool amazon_jobs_search
/amazon-jobs/jobReturns one Amazon.jobs posting by its numeric job id (the `id` field returned by search). Parsed from amazon.jobs's stable server-rendered job detail page — there is no separate JSON detail endpoint upstream.
Response notes
- An unknown or no-longer-listed job id returns `404`. - `description`, `basic_qualifications`, and `preferred_qualifications` are HTML-stripped plain text, parsed from the detail page. - `schedule_type` and `posted_at` are only populated by the search endpoint's richer JSON payload; the detail page does not expose them, so they are omitted here. Example response: ```json { "code": 200, "msg": "OK", "data": { "id": "10386857", "title": "Software Engineer", "company": "Amazon Web Services Australia Pty Ltd", "location": "AUS, NSW, Sydney", "city": "Sydney", "state": "NSW", "country": "AUS", "category": "Software Development", "description": "AWS Infrastructure Services owns the design, planning, delivery, and operation of all AWS global infrastructure...", "basic_qualifications": "Bachelor's degree in Computer Science or other technical degree or related experience...", "preferred_qualifications": "Experience building complex software systems that have been successfully delivered to customers...", "url": "https://www.amazon.jobs/en/jobs/10386857", "apply_url": "https://www.amazon.jobs/applicant/jobs/10386857/apply" } } ```
MCP tool amazon_jobs_job
Related APIs
Business & Market Intelligence
Turn public GitHub ecosystem signals into structured data for developer-market research, open-source intelligence, recruiting, and AI-agent workflows.
Business & Market Intelligence
Collect public TrustMRR startup marketplace and leaderboard data as normalized JSON for startup research, SaaS discovery, and market intelligence workflows.
Business & Market Intelligence
Add website and competitive intelligence signals from SimilarWeb to research pipelines.
Related dataset
Dataset · queryable JSON
Amazon's open postings are also queryable in bulk alongside 18 other providers — filter by department, location, employment type, or remote flag over one REST call.
Explore the dataset →How to scrape Amazon Jobs
amazon.jobs runs its own search API, separate from any shared ATS — a plain scraper has to reverse-engineer Amazon's own category taxonomy and pagination. Crawlora's Amazon Jobs endpoints return normalized postings directly, no per-category scraper to maintain.
Search by free-text query, one of Amazon's own job-category taxonomy slugs (e.g. software-development), an ISO country code, or any combination.
Pass the query/category/country to Crawlora's Amazon Jobs search endpoint — sortable by relevance or recency.
Receive normalized postings — title, location, category, apply URL — in one JSON shape, or fetch one posting in full by its numeric job id.
Monitor a category or country over time for hiring-trend signals, or aggregate alongside the Jobs dataset for talent-market research.
FAQ
Send a keyword, category, or country to Crawlora's Amazon Jobs search endpoint and get normalized postings — title, location, category, apply URL — without reverse-engineering amazon.jobs's own category taxonomy or pagination. Collect only public data and respect Amazon's terms.
Amazon's own taxonomy — software-development, data-science, business-intelligence-data-engineering, fulfillment-center-warehouse-associate, and dozens more — passed as the category parameter; either category or a free-text q is required.
Yes — pass the numeric Amazon job id to the single-posting endpoint for the full listing.