Local business and POI data collection
Use Apple Maps endpoints to turn local business and poi data collection into repeatable API requests with documented inputs and JSON responses.
Turn Apple Maps' public data into structured JSON — keyword and category place search around a coordinate, typeahead suggestions, full place detail (singly or 20 at a time) with the complete photo set, reverse geocoding, driving/walking/cycling directions and cheaper travel-time-only estimates, live transit departures for a stop, indoor venue directories for malls and airports, and the whole Apple Guides editorial layer by city, publisher, or coordinate. Credential-free.
Search Apple Maps places, get full place detail and photos, reverse-geocode, route between points, and browse Apple Guides as JSON.
Endpoint families
6
Documented params
111
Examples
19
Live catalog snapshot
Active endpoints
19
Methods
GET
Required params
50
Schema refs
19
{
"platform": "Apple Maps",
"endpoint": "apple-maps-search",
"method": "GET",
"path": "/apple-maps/search",
"auth": "apiKey"
}Use cases
Search Apple Maps places, get full place detail and photos, reverse-geocode, route between points, and browse Apple Guides as JSON.
Use Apple Maps endpoints to turn local business and poi data collection into repeatable API requests with documented inputs and JSON responses.
Use Apple Maps endpoints to turn location intelligence and footfall research into repeatable API requests with documented inputs and JSON responses.
Use Apple Maps endpoints to turn routing, travel-time, and transit analysis into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live Apple Maps endpoint catalog — 19 endpoints, 111 documented request parameters, and 19 published response schemas — the same catalog Docs and Playground run against.
19 documented Apple Maps endpoints, grouped into 12 request families — Guides, Place and Autocomplete, plus 9 more.
111 request parameters are documented across those Apple Maps endpoints, 50 of them required — the full input contract is public before you write any integration code.
19 of the 19 Apple Maps endpoints ship a recorded example response, and 19 carry a documented response schema — you can code against the real JSON before the first request.
Apple Maps endpoints document their error responses (400, 404 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.
19 hosted MCP tools back the Apple Maps endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
These cards are generated from the active endpoint catalog, so the landing page reflects the same API surface used by Docs and Playground.
/apple-maps/guides
/apple-maps/place
/apple-maps/autocomplete
/apple-maps/categories
/apple-maps/category-search
/apple-maps/directions
Featured endpoints
/apple-maps/searchReturns Apple Maps places matching a keyword, business name, category, or street address near a coordinate. Each place carries its Apple place ID (the value the place endpoint takes), name, category, coordinates, formatted and structured address, phone, website, rating and review count, price level, weekly opening hours, and a hero photo. Apple returns a bounded set per viewport (around 25 places for the default span) with no pagination; widen the span or move the center to cover more area. When nothing matches near the center Apple may relocate the search to a default region, reported by relocated=true and the region bounds. The response's filters block lists the refinement chips Apple offers for this query and area (open now, top rated, in guides, cuisines, price bands, amenities, accolades, sort); pass their keys back as filters and sort to refine the same search.
MCP tool apple_maps_search
/apple-maps/placeReturns one Apple Maps place by its place ID: name, type, category taxonomy, coordinates, formatted and structured address, phone numbers, website, rating and review count, price level, weekly opening hours, amenities (payment, accessibility, parking, and similar yes/no attributes), photos, review snippets (text, rating, time, and source link, without reviewer identity), the business-claim link, and the IDs of Apple Guides that include the place. Accepts either the external place ID (starts with I, the place-id= value in a maps.apple.com/place URL) or the numeric ID from a search result.
MCP tool apple_maps_place
/apple-maps/placesReturns the same full detail as the place endpoint for up to 20 place IDs in a single upstream call, plus the list of requested IDs Apple did not return. Accepts the external I... form and the numeric id interchangeably.
MCP tool apple_maps_places
/apple-maps/place/photosReturns all of a place's photos (the place endpoint caps at 20): the business cover photo first when present, then the hero photo, then every categorized photo with its category (Food & Drink, Interior, Exterior, ...), width and height.
MCP tool apple_maps_place_photos
/apple-maps/category-searchReturns places in one browse category near a coordinate without a keyword, in the same shape as the search endpoint (place summaries, region, relocation flag, and the refinement filters block). The category is a name from the categories endpoint for the same area (case-insensitive) or its key; an unknown name returns 400 listing the categories available there. Filters and sort work exactly as on the search endpoint.
MCP tool apple_maps_category_search
/apple-maps/categoriesReturns the "Find Nearby" browse categories Apple Maps offers for an area (for example Restaurants, Coffee Shops, Gas Stations, Hotels, Parking, Grocery Stores), each with the key and name the category-search endpoint takes. The set is location-aware.
MCP tool apple_maps_categories
Related APIs
Maps & Local Data
Collect local business and place data from Google Maps for location intelligence workflows.
Maps & Local Data
Search ready-made scraped datasets for local business research with filters, facets, geo queries, and repeatable API output.
Maps & Local Data
Normalize location search, coordinate lookup, and OSM identifier enrichment through API-key protected geocoding endpoints.
How to scrape Apple Maps
Crawlora's Apple Maps endpoints return normalized public Apple Maps data as JSON with one API key — no Apple developer account, MapKit token, or signed JWT required. Place lookups are viewport-based rather than paginated, so the search center and span do the work a page cursor would elsewhere.
The search endpoint takes a query — a keyword, business name, category, or street address — plus a latitude and longitude, and returns the places Apple shows for that viewport. span sets the viewport size in degrees and defaults to roughly a 5km box; lang and country select Apple's display language and regional catalog. There is no pagination: move the center or widen span to cover more ground. To browse without a keyword, list the Find Nearby categories for an area and pass one to the category-search endpoint.
The place endpoint returns a single place's complete detail by its place ID, which every search result carries. When you are enriching a list, the places endpoint takes up to 20 IDs and resolves them all in one upstream call. Place detail caps its inline photo array at 20 — use the place-photos endpoint for the full set.
The reverse-geocode endpoint turns a coordinate into Apple's own address record. For movement between two points, the directions endpoint returns driving, walking, or cycling routes with optional intermediate stops, while the ETA endpoint returns just the travel time and distance — the cheaper call when the route geometry is not needed.
The transit-departures endpoint returns a stop or station's systems, lines, and upcoming departures with real-time status. The venue-browse endpoint returns the indoor directory for the venues Apple has floor data for — malls, airports, stadiums — and, with a category, the stores and places inside them.
Apple Guides are publisher-curated place collections, and they have their own family here: the guides home page worldwide or for one city, the city picker behind it, the guides curated around a coordinate, the Browse by Publisher list, one publisher's profile and guides, one guide with every place in it, and a lookup that resolves up to 20 guide ids at once — including the guide ids a place record itself carries.
FAQ
Search places near a coordinate, then read one place's full detail by its place ID (or up to 20 at once), pull its complete photo set, reverse-geocode coordinates, request routes or travel-time estimates, and browse the Apple Guides layer — all return structured JSON with one API key.
No. Every Apple Maps endpoint here reads credential-free public Apple Maps data and authenticates with your Crawlora API key alone — there is no Apple developer account, MapKit JS token, or signed JWT anywhere in the flow.
You do not — Apple Maps search is viewport-based, not paginated. Widen span to cover a larger box, or move the latitude/longitude center and search again. limit caps how many places come back for the viewport you asked for, defaulting to 25.
When nothing matches near the center, Apple relocates the search to a default region rather than returning an empty list. The response flags this with relocated, and region carries the bounding box the results actually came from — check both before treating the places as local.
Apple Guides are curated place collections published by third-party editorial partners inside Apple Maps. The full layer is covered: the guides home page worldwide or per city, the city and publisher browse lists, one publisher's guides, one guide with every place in it, the guides curated around a coordinate, and a batch lookup that resolves up to 20 guide ids at once.