Apple Jobs location discovery API

Endpoint facts

Method

GET

API path

/apple-jobs/locations

Auth

apiKey

Credits

1 credit/request

Platform

Apple Jobs

Response schema

#/definitions/applejobs.locationsResponseDoc

Overview

Discovery endpoint for apple-jobs-search's `location` parameter, whose accepted values are a closed set Apple itself defines (its own `<slug>-<CODE>` location ids -- free-text location names are rejected by the search backend). Apple exposes no bulk "list everything" API for this; its only source is its own location-filter typeahead, a fuzzy search capped at 10 results per call covering four granularities (country, state/province, metro area, city) with no empty-input listing mode. With no `q`, this returns the full country-level value space (206 values, live-verified) as a static list -- the granularity apple-jobs-search's own examples use and nearly every caller needs, with no live upstream call required. With `q` supplied, this instead live-proxies Apple's own typeahead so callers can discover state/metro/city-level values for finer filtering; results at those deeper levels may include more than one candidate and are ranked by Apple's own relevance, not alphabetically. 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.

Authentication

Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.

Billing

Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.

Credit cost

1 credit/request

Charged response

Successful 2xx responses

Infrastructure behavior

This endpoint is executed through Crawlora's managed scraping infrastructure.

• Proxy strategy: managed automatically where needed
• Browser rendering: enabled for supported targets that require rendered HTML or JavaScript execution
• Browser cluster: supported dynamic workloads can be routed through distributed browser instances
• Retry behavior: automatic retry/fallback may be used depending on endpoint type
• Challenge handling: challenged pages or unusable upstream HTML are detected and surfaced clearly when they cannot be used
• Billing: credits are charged only for successful 2xx responses
• Observability: responses include request context where available

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): ```json { "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`): ```json { "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" } } ```

Error behavior

Crawlora does not silently return bad data when the upstream page cannot be used.

When possible, Crawlora returns structured error context so your integration can retry, back off, or inspect the request.

Related