Meta Jobs

Meta Jobs search

Searches 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.

get/meta-jobs/search

Request

  • Base URL: https://api.crawlora.net/api/v1
  • URL: https://api.crawlora.net/api/v1/meta-jobs/search
  • Auth: API key in header x-api-key

Query parameters

qstring

Facet-name keyword: matches team, technology, location, or ref/req-code -- not a title/description search

teamsstring[]

Repeatable team-or-technology filter (OR); see teams enum above

rolesstring[]

Repeatable employment-type filter (OR); see roles enum above

officesstring[]

Repeatable location-id filter (OR) in Meta's own id format, e.g. menlo-park, london -- not a closed enum

is_remote_onlyboolean

Restrict to remote-only postings

sort_by_newboolean

Sort newest-first instead of relevance

results_per_page'all' | 'five' | 'ten'

Response size cap: all, five, ten

Headers

x-api-keystring required

API key required

Response

OK

codeinteger
msgstring

Example response

{
  "code": 200,
  "data": {
    "jobs": [
      {
        "id": "1010234865172301",
        "locations": [
          "Sunnyvale",
          " CA"
        ],
        "sub_teams": [
          "Hardware"
        ],
        "teams": [
          "Infrastructure"
        ],
        "title": "ASIC Engineer, Design",
        "url": "https://www.metacareers.com/profile/job_details/1010234865172301/"
      }
    ],
    "total": 58
  },
  "msg": "OK"
}

Changes

No recorded changes to this operation across all 4 revisions of this API.