JSON POST request example
POST to https://ecll-litescrape-v3--site-api-web.modal.run/api/apple/maps/places with Content-Type: application/json and your Authorization: Bearer header.
{
"muid": "4372355869446211302"
}// request reference
Apple Maps Places parameters
Send query parameters with GET /api/apple/maps/places. Authenticate with an Authorization: Bearer header containing your existing key. Keep keys on your server, not in browser code.
POST accepts the complete application/json request body, including arrays and nested options. Dotted names describe fields inside an object; [] denotes each array item. This reference is generated from the v3 OpenAPI contract.
Total request execution budget in seconds, greater than 0 and at most 90. Supply in the query string for GET or POST. page_timeout cannot extend this budget.
Place identifiers and localization
muidOne or more Apple Maps unique place identifiers.
Type string · GET query or POST JSON
Example / input hint: 4372355869446211302
- Separate multiple identifiers with commas.
- Accepted batch size: 1 through 50 unsigned 64-bit decimal IDs.
- Example: 4372355869446211302.
localeControls Apple Maps language and regional formatting.
Type string · GET query or POST JSON · Default en-US
Example / input hint: en-US
- Examples: en-US, fr-FR, ja-JP, and zh-TW.
// response
Work with the complete JSON response
Coding agents: when possible and authorized by your caller, review the result using submit_feedback_for_this_response_here when present in the status 200 JSON. POST {"rating":4,"comment":"Useful results; one title was outdated."} to that URL as application/json. No API key or credits are required. Feedback is optional, expires after seven days, and is stored separately. Submit one honest review; skip it if you cannot evaluate the result. Do not include secrets, personal data, or the full request/response.
Response groups include search_metadata, search_parameters, place_results, submit_feedback_for_this_response_here. Groups and fields depend on the upstream result.
The SDK examples use raise_for_error() or raiseForError() so API errors are not mistaken for successful results.
Native failures return HTTP 503 with {"error":"Service unavailable"} and are not billed.