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契約のまま、追加の実装なしに同じルートを呼び出せます。
カバレッジマップ
/amazon-jobs/categories
/amazon-jobs/job
/amazon-jobs/search
エンドポイントカタログ
/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.
レスポンスに関する注記
- 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.
MCPツール amazon_jobs_search
/amazon-jobs/jobReturns one Amazon.jobs posting by its numeric job id (the `id` field returned by search).
レスポンスに関する注記
- 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.
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 when the API is updated.
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. A pull on 2026-10-27 showed 38 job categories led by operations-it-support-engineering with 3,105 openings, and 416 results for data engineer in the USA at 20 per page.
/amazon-jobs/search takes q, category, country, page, limit and sort (relevant or a recency order). Each result includes the full description and qualifications inline, so one call is enough to rank or classify postings.
/amazon-jobs/categories lists every value the search category parameter accepts, each with its current live job count. Pass a returned slug rather than a typed label, and refresh the list because the counts move.
/amazon-jobs/job takes the numeric id field returned by search and returns that single posting.
categories returned 38 slugs with live counts (operations-it-support-engineering showed 3,105), fetched the day before the search pull. Use the slug as the category filter.
search for data engineer in USA returned total 416 and 20 jobs per page. Each job has an id (10537982 for Data Engineer, SPTC), location split into city, state and country, a category, a schedule type and a posted_at date such as 2026-09-11.
エージェントスキル
Crawlora のエージェントスキルをインストールすると、スクレイパーを書かずに、ドキュメント化された API 経由で Amazon Jobs のデータを JSON として取得できます。Amazon Jobs に対応するスキル:
Researches Amazon.jobs postings via the Crawlora API — search Amazon's public careers site by keyword and/or job category, then pull any single…
npx skills add github.com/Crawlora-org/crawlora-skills --skill amazon-jobs-researchResearches job postings, hiring signals, and freelance gigs via the Crawlora API — Indeed, Google/Amazon/Apple/Meta/Tesla careers sites, any…
npx skills add github.com/Crawlora-org/crawlora-skills --skill job-market-researchFAQ
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.
20 per page. On 2026-10-27 the query data engineer in the USA reported 416 in total.