Meta hiring-trend tracking
Mit Meta Jobs-Endpunkten verwandelst du meta hiring-trend tracking in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Search Meta's own careers site (metacareers.com) — by team, employment type, or office — list its full open-requisition catalog in one call, or get a single posting by id, as structured JSON.
Search Meta's own careers site (metacareers.com) by team, role, or office, list the full catalog, or get one posting by id, as structured JSON.
Endpunkt-Familien
3
Dokumentierte Parameter
13
Beispiele
3
Live-Katalog-Snapshot
Aktive Endpunkte
3
Methoden
GET
Pflichtparameter
4
Schema-Referenzen
3
{
"platform": "Meta Jobs",
"endpoint": "meta-jobs-search",
"method": "GET",
"path": "/meta-jobs/search",
"auth": "apiKey"
}Use Cases
Search Meta's own careers site (metacareers.com) by team, role, or office, list the full catalog, or get one posting by id, as structured JSON.
Mit Meta Jobs-Endpunkten verwandelst du meta hiring-trend tracking in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit Meta Jobs-Endpunkten verwandelst du job posting aggregation and monitoring in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit Meta Jobs-Endpunkten verwandelst du recruiting and talent-market research in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Managed Execution
Jede Zahl unten stammt direkt aus dem Live-Meta Jobs-Endpunktkatalog — 3 Endpunkte, 13 dokumentierte Request-Parameter und 3 veröffentlichte Response-Schemas — demselben Katalog, gegen den auch Docs und Playground laufen.
3 documented Meta Jobs endpoints, grouped into 3 request families — Job, List and Search.
13 request parameters are documented across those Meta Jobs endpoints, 4 of them required — the full input contract is public before you write any integration code.
3 of the 3 Meta 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.
Meta 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 Meta Jobs endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Abdeckungskarte
/meta-jobs/job
/meta-jobs/list
/meta-jobs/search
Endpunktkatalog
/meta-jobs/searchSearches Meta's public careers site (metacareers.com) with the same team/technology/location/employment-type/keyword/remote/sort filters the live search page offers. All filters are optional and combine with AND semantics; an empty request returns Meta's entire open-requisition catalog in one response. `q` matches team, technology, location, or ref/req-code names -- it is NOT a free-text search over job titles or descriptions. `teams` enum (org teams + technologies, both use the same field): `Advertising Technology`, `AR/VR`, `Artificial Intelligence`, `Business Development & Partnerships`, `Communications & Public Policy`, `Creative`, `Data & Analytics`, `Data Center`, `Design & User Experience`, `Enterprise Engineering`, `Global Operations`, `Infrastructure`, `Internship - Business`, `Internship - Engineering, Tech & Design`, `Internship - PhD`, `Legal, Finance, Facilities & Admin`, `People & Recruiting`, `Product Management`, `Research`, `Sales & Marketing`, `Security`, `Software Engineering`, `Technical Program Management`, `University Grad - Business`, `University Grad - Engineering, Tech & Design`, `University Grad - PhD & Postdoc`, `Facebook`, `Messenger`, `Instagram`, `WhatsApp`, `Meta Quest`. `roles` enum: `Full time employment`, `Internship`, `Short term employment`. `results_per_page` enum: `all`, `five`, `ten`.
Hinweise zur Response
- A valid filter combination with no matches returns `total: 0` and an empty `jobs` array (not an error). - Meta's unfiltered catalog is roughly 750 open roles; even an unfiltered search returns everything in one response. There is no page/offset parameter beyond `results_per_page`, because Meta's own search page does not expose one past that cap. - An invalid `teams`, `roles`, or `results_per_page` value returns a `400` invalid-params error rather than being silently dropped or passed through to the upstream. - `jobs[].teams` and `jobs[].sub_teams` are Meta's own tags on the posting and may include values beyond what you filtered on (a posting can carry multiple teams).
MCP-Tool meta_jobs_search
/meta-jobs/listReturns a page of Meta's own public job sitemap -- every open requisition's id, canonical URL, and last-modified timestamp, with no team/location/keyword filtering. Use this for full-catalog enumeration or change tracking via last_modified; use search when you need to filter by team, technology, location, employment type, or keyword.
Hinweise zur Response
- A page beyond `total` returns an empty `listings` array (not an error). - `listings[].last_modified` reflects Meta's own sitemap timestamp and is the only signal this endpoint gives for change detection — it carries no title/team/location metadata. Call [job](meta-jobs-job.md) for the full posting.
MCP-Tool meta_jobs_list
/meta-jobs/jobReturns one Meta Careers posting by its numeric job id (the `id` field returned by search or list).
Hinweise zur Response
- A nonexistent or removed job id returns a `404` (Meta's own job detail page structurally signals this — it is not inferred from an HTTP status alone). - `description` is cleaned plain text; Meta serves it as HTML internally. - `compensation_min`/`compensation_max`/`compensation_country` are only present for postings that carry Meta's public pay-range disclosure (not every posting does).
MCP-Tool meta_jobs_job
Verwandte 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.
Verwandtes Dataset
Dataset · abfragbares JSON
Meta'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.
Dataset erkunden →So scrapst du Meta Jobs
metacareers.com's own search facets aren't a title/description search — they match team, technology, location, or req code. Crawlora's Meta Jobs endpoints normalize postings directly, including a full-catalog listing call for metacareers.com's entire open-requisition set. A pull on 2026-10-27 showed the listing route returning 1,293 postings at 50 per page with local-offset timestamps, and a search for machine learning returning 170 jobs.
/meta-jobs/search takes q, teams, roles, offices, is_remote_only, sort_by_new and results_per_page, the same filters as the live careers search. Repeat a facet to OR its values.
/meta-jobs/list pages Meta's public job sitemap with page and page_size: every open requisition's id, canonical URL and last-modified timestamp, with no team, location or keyword filter.
/meta-jobs/job takes the numeric id returned by search or list and returns that one posting in full.
list returned total 1,293 with 50 per page, each row an id, URL and last_modified. Timestamps carried a -07:00 offset (2026-10-26T20:34:37-07:00), so normalize to UTC before comparing.
search for machine learning returned 170 jobs with title, locations, teams and sub_teams arrays; the first was Research Scientist Intern, AI Core Machine Learning (PhD) in London, UK. Team and location are lists, so one job can match several.
Agent Skills
Installiere einen Crawlora Agent Skill, und dein Agent ruft Meta Jobs-Daten als JSON über die dokumentierte API ab, ohne einen Scraper zu schreiben. Diese Skills decken Meta Jobs ab:
Searches and pulls postings from Meta's public careers site (metacareers.com) via the Crawlora API — full catalog listing, filtered search by…
npx skills add github.com/Crawlora-org/crawlora-skills --skill meta-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 team/technology, employment-type, or office facets to Crawlora's Meta Jobs search endpoint — or call the catalog-listing endpoint for metacareers.com's entire open-requisition set in one call — and get normalized postings without reverse-engineering Meta's own facet format. Collect only public data and respect Meta's terms.
No — the q parameter is a facet-name keyword matching team, technology, location, or ref/req code, not a free-text title/description search. Use the catalog-listing endpoint if you want every open role regardless of keyword.
Yes — pass the Meta job id to the single-posting endpoint for the full listing.
The list route's last_modified used a -07:00 offset on 2026-10-27, so convert to UTC.