Meta Jobs API endpoint
Use Crawlora's Meta Jobs search API to extract supported public Meta Jobs data as structured JSON. This page includes request parameters, cURL examples, response schema, error behavior, credit cost, and a Playground link for testing before integration.
/meta-jobs/searchSearches Meta's public careers site (metacareers.com) via its own anonymous jobsearch GraphQL endpoint, 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`. Developers commonly use this endpoint for data enrichment, monitoring, research dashboards, internal automation, and agent-native workflows that need repeatable structured public web data. Authentication uses the documented Crawlora headers, and usage is metered with the credit cost shown on this page.
Request parameters are generated from the active endpoint catalog. Required values must be sent before Crawlora can call the upstream public web data source.
| Parameter | Type | Required | Default | Description | Example |
|---|---|---|---|---|---|
| q | string | No | Facet-name keyword: matches team, technology, location, or ref/req-code -- not a title/description search | ||
| teams | array | No | Repeatable team-or-technology filter (OR); see teams enum above | ||
| roles | array | No | Repeatable employment-type filter (OR); see roles enum above | ||
| offices | array | No | Repeatable location-id filter (OR) in Meta's own id format, e.g. menlo-park, london -- not a closed enum | ||
| is_remote_only | boolean | No | Restrict to remote-only postings | ||
| sort_by_new | boolean | No | Sort newest-first instead of relevance | ||
| results_per_page | string | No | Response size cap: all, five, ten Allowed values: all, five, ten | ||
| x-api-key (header) | string | Yes | API key required |
curl -X GET "https://api.crawlora.net/api/v1/meta-jobs/search?q=coffee&is_remote_only=true&sort_by_new=true&results_per_page=all" \ -H "x-api-key: $CRAWLORA_API_KEY"
Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.
Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.
| Plan | Price | Included credits | Daily cap | Rate limit | Overage |
|---|---|---|---|---|---|
| Free | $0/mo | 2,000 | 500 daily credits | 5/min | No overage |
| Starter | $9/mo | 20,000 | 5,000 daily credits | 15/min | $0.75/1,000 overage credits when enabled |
| Growth | $29/mo | 100,000 | 25,000 daily credits | 45/min | $0.45/1,000 overage credits when enabled |
| Pro | $79/mo | 400,000 | No daily cap | 120/min | $0.30/1,000 overage credits |
| Business | $199/mo | 1,200,000 | No daily cap | 300/min | $0.20/1,000 overage credits |
| Enterprise | $499/mo | 5,000,000 | No daily cap | 1,000/min | $0.12/1,000 overage credits |
This endpoint is executed through Crawlora's managed scraping infrastructure.
- 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). Example response: ```json { "code": 200, "msg": "OK", "data": { "total": 58, "jobs": [ { "id": "1069625435495910", "title": "Product Designer, Meta Superintelligence Labs", "locations": ["Menlo Park, CA"], "teams": ["Artificial Intelligence", "Design & User Experience"], "sub_teams": ["Design", "Artificial Intelligence"], "url": "https://www.metacareers.com/profile/job_details/1069625435495910/" } ], "source_url": "https://www.metacareers.com/jobsearch/" } } ```
Crawlora does not silently return bad data when the upstream page cannot be used.
| Status | Common failure case |
|---|---|
| 400 | Invalid input or missing required parameter |
| 429 | Plan or endpoint rate limit exceeded |
| 500 | Internal execution error |
| 502 | Upstream platform failed, returned unusable HTML, or served a challenge page that could not be resolved |
When possible, Crawlora returns structured error context so your integration can retry, back off, or inspect the request.
| Status | Description | Schema |
|---|---|---|
| 400 | Bad Request | #/definitions/app.Response |
| 429 | Too Many Requests | #/definitions/app.Response |
| 503 | Service Unavailable | #/definitions/app.Response |
{
"code": 200,
"msg": "OK",
"data": {
"total": 58,
"jobs": [
{
"id": "1069625435495910",
"title": "Product Designer, Meta Superintelligence Labs",
"locations": [
"Menlo Park, CA"
],
"teams": [
"Artificial Intelligence",
"Design & User Experience"
],
"sub_teams": [
"Design",
"Artificial Intelligence"
],
"url": "https://www.metacareers.com/profile/job_details/1069625435495910/"
}
],
"source_url": "https://www.metacareers.com/jobsearch/"
}
}Request schema
No body schema
Response schema
#/definitions/metajobs.searchResponseDoc
| Field | Type | Required | Enum | Bounds | Example | Description |
|---|---|---|---|---|---|---|
| code | integer | No | 200 | |||
| data | metajobs.SearchResponse | No | ||||
| data.jobs | array | No | ||||
| data.jobs[].id | string | No | 1010234865172301 | |||
| data.jobs[].locations | array | No | Sunnyvale, CA | |||
| data.jobs[].sub_teams | array | No | Hardware | |||
| data.jobs[].teams | array | No | Infrastructure | |||
| data.jobs[].title | string | No | ASIC Engineer, Design | |||
| data.jobs[].url | string | No | https://www.metacareers.com/profile/job_details/1010234865172301/ | |||
| data.source_url | string | No | ||||
| data.total | integer | No | 58 | |||
| msg | string | No | OK |
Use environment variables for secrets and keep Crawlora API keys server-side.
curl -X GET "https://api.crawlora.net/api/v1/meta-jobs/search?q=coffee&is_remote_only=true&sort_by_new=true&results_per_page=all" \
-H "x-api-key: $CRAWLORA_API_KEY"Crawlora is designed for responsible structured public web data workflows. Customers are responsible for using Crawlora in compliance with applicable laws, third-party rights, target-platform rules, and Crawlora terms.
Read Crawlora terms