amazon.jobs APIamazon.jobs ↗
Search Amazon job listings by keyword, location, and category. Get full job details, team info, and qualifications via 3 structured endpoints.
curl -X GET 'https://api.parse.bot/scraper/c8e2ace2-fff0-4b07-88af-334f1ccb52ec/search_jobs?limit=5&query=software+engineer&offset=10&category=Data+Science' \ -H 'X-API-Key: $PARSE_API_KEY'
Search for Amazon job listings with keyword search, location/category filters, and pagination. Returns job listings with details and total hit count.
| Param | Type | Description |
|---|---|---|
| city | string | City filter (e.g., 'Seattle', 'San Francisco') |
| sort | string | Sort order: 'relevant' or 'recent' |
| limit | integer | Number of results per page (max varies, typically 10-100) |
| query | string | Search keyword/query (e.g., 'software engineer', 'data scientist') |
| offset | integer | Pagination offset (0-based) |
| region | string | State/region abbreviation filter (e.g., 'WA', 'CA', 'NSW') |
| country | string | 3-letter country code filter (e.g., 'USA', 'GBR', 'IND', 'AUS'). Uses ISO 3166-1 alpha-3 codes as returned in the country_code field of job results. |
| category | string | Job category filter (e.g., 'Software Development', 'Data Science'). Use get_job_categories for valid values. |
{
"type": "object",
"fields": {
"jobs": "array of job objects with id, title, company, location, category, posted_date, and other fields",
"limit": "integer, results per page requested",
"offset": "integer, current pagination offset",
"total_hits": "integer, total number of matching jobs",
"jobs_returned": "integer, number of jobs in this response"
},
"sample": {
"data": {
"jobs": [
{
"id": "3092179",
"city": "San Francisco",
"state": "CA",
"title": "Software Engineer",
"company": "Twitch Interactive, Inc. - D48",
"category": "Software Development",
"job_path": "/en/jobs/3092179/software-engineer",
"location": "US, CA, San Francisco",
"job_family": "Software Development",
"posted_date": "September 24, 2025",
"country_code": "USA",
"updated_time": "5 days",
"schedule_type": "full-time",
"url_next_step": "https://account.amazon.com/jobs/3092179/apply",
"business_category": "subsidiaries",
"description_short": "If you are interested in this position...",
"normalized_location": "San Francisco, California, USA",
"basic_qualifications": "- Bachelor's degree...",
"preferred_qualifications": "- Experience with AWS..."
}
],
"limit": 5,
"offset": 0,
"total_hits": 1702,
"jobs_returned": 5
},
"status": "success"
}
}About the amazon.jobs API
The Amazon Jobs API provides 3 endpoints for searching and retrieving job listings from amazon.jobs. Use search_jobs to query across thousands of open positions with keyword, location, category, and country filters, then call get_job_details with a specific iCIMS job ID to retrieve the full job description, qualifications, team metadata, and location details for any listing.
Searching Jobs
The search_jobs endpoint accepts a query string (e.g., 'software engineer') alongside optional filters for city, region (state abbreviation like 'WA'), country (ISO 3166-1 alpha-3 codes like 'USA' or 'GBR'), and category. Results are paginated via offset and limit parameters, and the response includes total_hits so you can calculate page counts before fetching subsequent pages. Sort order can be set to 'relevant' or 'recent' depending on your use case.
Job Details
Each object in the jobs array from search_jobs includes an id field — the iCIMS job ID — which you pass to get_job_details. That endpoint returns the full job record: title, company, category, city, state, location, job_path, a team object with team metadata, an internal uuid, and the complete job description and qualifications text not available in search results.
Categories
The get_job_categories endpoint returns a jobCategories array, where each entry includes an arsIdentifier, displayName, identifier, description, and url. These identifier values map directly to the category filter in search_jobs, so you can enumerate all valid categories before constructing filtered queries rather than guessing category strings.
- Build a job alert system that polls
search_jobswith specific keywords and notifies users when new listings appear via theposted_datefield - Aggregate Amazon job openings by country and region using the
countryandregionfilters to produce geographic hiring dashboards - Classify and count open roles by team or category using
get_job_categoriesand thecategoryfield returned in search results - Feed a recruiting CRM with structured job data including
title,location,company, andjob_pathfor each open position - Track hiring volume over time by recording
total_hitsfor repeated queries across different categories or locations - Surface relevant Amazon positions in a developer-facing job board filtered to
'Software Development'or'Data Science'categories
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Amazon Jobs have an official public developer API?+
What does `get_job_details` return beyond what `search_jobs` provides?+
get_job_details returns the full job record for a single position, including the complete job description text, qualifications, a team object with team metadata, and an internal uuid. The search_jobs endpoint returns a summary view — title, company, location, category, posted_date, and id — but omits the full description and team details that get_job_details exposes.How does pagination work in `search_jobs`?+
search_jobs endpoint uses offset and limit parameters. The response includes total_hits (total matching jobs), jobs_returned (jobs in the current response), and the offset you sent. To retrieve the next page, increment offset by limit. For example, with limit=10, page two starts at offset=10.Does the API return saved job applications or candidate profile data?+
Can I filter jobs by salary or compensation range?+
search_jobs or get_job_details response shapes. The API covers job metadata, description text, location, and team fields. You can fork this API on Parse and revise it to add compensation filtering if Amazon Jobs exposes that data for a specific role type.