Apple Jobs location discovery API

Endpoint facts

Method

GET

API path

/apple-jobs/locations

Auth

apiKey

Credits

1 credit/request

Charged on

Successful 2xx responses only

Platform

Apple Jobs

Response schema

#/definitions/applejobs.locationsResponseDoc

How this endpoint behaves

Apple exposes no bulk "list everything" API for this. Its only upstream source is its own location-filter typeahead (the same one the jobs.apple.com search page's location filter calls as you type), a fuzzy search capped at 10 results per call that covers four distinct granularities — country, state/province, metro area, and city — with no empty-input or list-all mode.

Query parameters:

• q (optional): free-text location search, e.g. singapore or cupertino.
  • Omitted: returns the full country-level value space — 206 values, live-verified 2026-09-16 — as a static list. This is the granularity apple-jobs-search's own documented examples use (united-states-USA, singapore-SGP) and covers nearly every caller's needs with no live upstream call.
  • Supplied: searches Apple's own location typeahead, so callers can discover state/metro/city-level values too (e.g. q=cupertino returns cupertino-california-united-states-CUP). Results can include more than one candidate and are ranked by Apple's own relevance, not alphabetically. Not every country/state/city Apple's site knows about will match a given q — this is the live, capped search Apple's own frontend uses, not an exhaustive index.

Notable response behavior:

• scope is country for the default (no-q) response, or search when q was supplied.
• Each locations[].location value is exactly what apple-jobs-search's location parameter expects.
• locations[].level is one of country, state, metro, city, or other (an unrecognized upstream level, included rather than silently dropped).
• Not every UN member state appears in the country list — Apple's own location taxonomy omits countries where it has no careers presence (e.g. Cuba, Iran, North Korea returned no match during live verification). The 206 values here are exactly what Apple's own reference data returns, not a general country-code list.
• A q result's location slug is computed the same way Apple's own frontend computes it (lowercase, non-alphanumeric runs collapsed to a single hyphen, trimmed) and has been verified correct for every case checked, including multi-word/parenthetical country names and city-level results. A city/metro/state name containing non-ASCII characters is the one case this cannot guarantee byte-for-byte, since Apple's own JS may normalize diacritics differently — treat those specific results as best-effort.

Example response (q omitted):

{
  "code": 200,
  "msg": "OK",
  "data": {
    "scope": "country",
    "count": 206,
    "locations": [
      {"location": "singapore-SGP", "name": "Singapore", "code": "SGP", "level": "country"},
      {"location": "united-states-USA", "name": "United States", "code": "USA", "level": "country"}
    ],
    "source_url": "https://jobs.apple.com/api/v1/refData/postlocation",
    "fetched_at": "2026-09-16T12:00:00Z"
  }
}

Example response (q=cupertino):

{
  "code": 200,
  "msg": "OK",
  "data": {
    "query": "cupertino",
    "scope": "search",
    "count": 2,
    "locations": [
      {"location": "cupertino-california-united-states-CUP", "name": "Cupertino, California, United States", "code": "CUP", "level": "city"},
      {"location": "santa-clara-valley-cupertino-california-united-states-SCV", "name": "Santa Clara Valley (Cupertino), California, United States", "code": "SCV", "level": "city"}
    ],
    "source_url": "https://jobs.apple.com/api/v1/refData/postlocation?input=cupertino",
    "fetched_at": "2026-09-16T12:00:00Z"
  }
}

Sampled response

Request, 14 Oct 2026

GET /apple-jobs/locations

Items in locations

206

Fields filled in every checked item

4

Shared guides

Related