Amazon hiring-trend tracking
Amazon Jobsエンドポイントを使えば、「Amazon hiring-trend tracking」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
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.
エンドポイントファミリー
3
ドキュメント化されたパラメータ
10
サンプル数
3
ライブカタログスナップショット
稼働エンドポイント
3
メソッド
GET
必須パラメータ
4
スキーマ参照
3
{
"platform": "Amazon Jobs",
"endpoint": "amazon-jobs-search",
"method": "GET",
"path": "/amazon-jobs/search",
"auth": "apiKey"
}ユースケース
Search Amazon's own careers site (amazon.jobs) by keyword, category, or country and get one posting by id, as structured JSON.
Amazon Jobsエンドポイントを使えば、「Amazon hiring-trend tracking」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Amazon Jobsエンドポイントを使えば、「Job posting aggregation and monitoring」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Amazon Jobsエンドポイントを使えば、「Recruiting and talent-market research」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
マネージド実行
以下の数値はすべて、稼働中のAmazon Jobsエンドポイントカタログから取得しています（エンドポイント3件、ドキュメント化されたリクエストパラメータ10個、公開レスポンススキーマ3件）。DocsとPlaygroundが参照しているカタログと同じものです。
Amazon Jobsのエンドポイントは3件、3つのリクエストファミリーに分類されています（Categories、Job、Search）。
これらのAmazon Jobsエンドポイントには10個のリクエストパラメータがドキュメント化されており、うち4個が必須です。統合コードを書く前に入力仕様をすべて確認できます。
3件のAmazon Jobsエンドポイントのうち3件が実際のサンプルレスポンスを、3件がドキュメント化されたレスポンススキーマを備えています。最初のリクエストの前に実データの形に合わせて実装できます。
Amazon Jobsのエンドポイントは成功時のスキーマに加えてエラーレスポンス（400、404、429、503）もドキュメント化しています。ブロック、レート制限、レコード欠損は空データではなく型付きのエラーとして返ります。
Amazon Jobsのエンドポイントは3個のホスト型MCPツールとして提供されており、エージェントは同じパラメータと同じJSON契約のまま、追加の実装なしに同じルートを呼び出せます。
カバレッジマップ
これらのカードは稼働中のエンドポイントカタログから生成されるため、このページはDocsとPlaygroundが使うAPIサーフェスをそのまま反映します。
/amazon-jobs/categories
/amazon-jobs/job
/amazon-jobs/search
エンドポイントカタログ
/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. See `amazon-jobs-categories` for the full, live-verified list of accepted `category` values.
レスポンスに関する注記
- 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. 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ツール 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.
レスポンスに関する注記
- 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ツール 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.
レスポンスに関する注記
- `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 on a code update -- see `notes/amazonjobs-maintenance.md`. Example response: ```json { "code": 200, "msg": "OK", "data": { "categories": [ {"category": "operations-it-support-engineering", "count": 3465}, {"category": "software-development", "count": 2614}, {"category": "fulfillment-operations-management", "count": 2240}, {"category": "database-administration", "count": 18} ], "count": 38, "source_url": "https://www.amazon.jobs/en/search.json?facets%5B%5D=category&offset=0&result_limit=1&sort=relevant", "fetched_at": "2026-09-16T00:00:00Z" } } ```
MCPツール amazon_jobs_categories
関連API
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.
関連データセット
データセット · クエリ可能な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.
データセットを見る →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.