Find the area ids that the search endpoints take, from `GET /api/booli/areas`. Send `query` for autocomplete (municipalities, counties, districts and streets with their parent) or `ids` to resolve known area ids to names and types. Send exactly one of the two.
Run this endpoint
Endpoint
Parameters
Start with the required fields, then add optional filters only when your use case needs them.
Runnable path
This endpoint has no required query parameters.
2 optional filters available.
string
Optional
Text to autocomplete, for example Stockholm. Send this or ids
coffee shops
string
Optional
Comma-separated area ids to resolve, for example 1,2. Send this or query
example
Response Schema
Example response fields are illustrative; inspect the JSON before integrating.
Example response fields
Scan these fields before integrating.
data
success
{
"data": {
"areas": [],
"count": 10,
"query": "stockholm"
},
"success": true
}
Errors
Handle these documented responses before retrying or showing customer-facing failures.
HTTP 404
The id, area or home does not exist. This response is not billable.
HTTP 422
A parameter or filter is missing or invalid. This response is not billable.
HTTP 503
Booli is temporarily unavailable. Retry the request. This response is not billable.
Generate Code with AI
Copy a ready-made prompt with all the endpoint details, parameters, and example responses. Paste it into ChatGPT, Claude, or any AI assistant to instantly generate working code.
Try It Live
Test this endpoint in our interactive playground with real data.