Amazon hiring-trend tracking
Usa los endpoints de Amazon Jobs para convertir amazon hiring-trend tracking en solicitudes API repetibles con inputs documentados y respuestas JSON.
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.
Familias de endpoints
3
Parámetros documentados
10
Ejemplos
3
Snapshot en vivo del catálogo
Endpoints activos
3
Métodos
GET
Parámetros obligatorios
4
Referencias de esquema
3
{
"platform": "Amazon Jobs",
"endpoint": "amazon-jobs-search",
"method": "GET",
"path": "/amazon-jobs/search",
"auth": "apiKey"
}Casos de uso
Search Amazon's own careers site (amazon.jobs) by keyword, category, or country and get one posting by id, as structured JSON.
Usa los endpoints de Amazon Jobs para convertir amazon hiring-trend tracking en solicitudes API repetibles con inputs documentados y respuestas JSON.
Usa los endpoints de Amazon Jobs para convertir job posting aggregation and monitoring en solicitudes API repetibles con inputs documentados y respuestas JSON.
Usa los endpoints de Amazon Jobs para convertir recruiting and talent-market research en solicitudes API repetibles con inputs documentados y respuestas JSON.
Ejecución gestionada
Cada cifra de abajo se lee directamente del catálogo de endpoints en vivo de Amazon Jobs — 3 endpoints, 10 parámetros de solicitud documentados y 3 esquemas de respuesta publicados — el mismo catálogo contra el que corren Docs y Playground.
3 documented Amazon Jobs endpoints, grouped into 3 request families — Categories, Job and Search.
10 request parameters are documented across those Amazon Jobs endpoints, 4 of them required — the full input contract is public before you write any integration code.
3 of the 3 Amazon Jobs endpoints ship a recorded example response, and 3 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.
3 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.
Mapa de cobertura
/amazon-jobs/categories
/amazon-jobs/job
/amazon-jobs/search
Catálogo de endpoints
/amazon-jobs/searchSearches Amazon's public careers site (amazon.jobs). Each result includes the full description and qualifications inline. `sort` accepts `relevant` (default, 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. See `amazon-jobs-categories` for the full, live-verified list of accepted `category` values.
Notas de la respuesta
- A valid query with no matches returns `total: 0` and an empty `jobs` array (not an error). A category can also legitimately have zero open postings at a given moment — check `amazon-jobs/categories`'s live count rather than assuming a `total: 0` response means the category value itself is wrong. - `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.
Herramienta MCP amazon_jobs_search
/amazon-jobs/jobReturns one Amazon.jobs posting by its numeric job id (the `id` field returned by search).
Notas de la respuesta
- An unknown or no-longer-listed job id returns `404`. - `description`, `basic_qualifications`, and `preferred_qualifications` are HTML-stripped plain text. - `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.
Herramienta MCP amazon_jobs_job
/amazon-jobs/categoriesLists every value amazon-jobs/search's `category` parameter accepts, each with its current live job count. Live-queries amazon.jobs's own search category facet rather than a static list, so counts and coverage stay current.
Notas de la respuesta
- `categories` is sorted by descending live `count`, ties broken alphabetically by `category`. - Every value below is currently accepted by `amazon-jobs/search`'s `category` parameter: `administrative-support`, `applied-science`, `audio-video-photography-production`, `business-intelligence`, `business-merchant-development`, `buying-planning-instock-management`, `corporate-operations`, `customer-service`, `data-science`, `database-administration`, `design`, `economics`, `editorial-writing-content-management`, `facilities-maintenance-real-estate`, `finance-accounting`, `fulfillment-associate`, `fulfillment-operations-management`, `fulfillment-warehouse-associate`, `hardware-development`, `human-resources`, `investigation-loss-prevention`, `leadership-development-training`, `legal`, `machine-learning-science`, `marketing-pr`, `medical-health-safety`, `operations-it-support-engineering`, `procurement`, `project-program-product-management-non-tech`, `project-program-product-management-technical`, `public-policy`, `public-relations`, `research-science`, `sales-advertising-account-management`, `software-development`, `solutions-architect`, `supply-chain-transportation-management`, `systems-quality-security-engineering`. - A category can report `count: 0` if amazon.jobs currently has no open postings in it; it is still a valid `category` input for `amazon-jobs/search` (it will just return an empty result page, not an error). - If amazon.jobs's own taxonomy changes (a category renamed, added, or removed upstream), this endpoint's counts reflect that immediately, but the accepted `category` slugs on `amazon-jobs/search` itself only change when the API is updated.
Herramienta MCP amazon_jobs_categories
APIs relacionadas
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.
Dataset relacionado
Dataset · JSON consultable
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.
Explorar el dataset →Cómo hacer scraping de 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.
Preguntas frecuentes
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.