Local POIs (Search API)
Requires API Key: Get one at https://api.search.brave.com
Plan: Included in the Search plan. See https://api-dashboard.search.brave.com/app/subscriptions/subscribe
Two-step flow: This endpoint requires POI IDs from a prior search.
- Get POI IDs from
local-place-search, or fromweb-searchwithresult_filter=locations(locations.results[].id)- Pass those IDs to this endpoint to get full business details
Quick Start (cURL)
Get POI Details
Multiple POIs with Location Headers
Note: POI IDs are opaque strings returned in web search locations.results[].id. IDs are ephemeral and expire after ~8 hours. The example IDs above are for illustration — fetch fresh IDs via web-search with result_filter=locations. Use --data-urlencode since IDs may contain =.
Endpoint
Authentication: X-Subscription-Token: <API_KEY> header
Parameters
Location Headers (Optional)
For distance calculation from user location:
Response Fields
The response has type: "local_pois" and a results array of LocationResult objects:
Example Response
Getting POI IDs
local-place-search returns POI IDs directly. They also come from the Web Search API (web-search) with result_filter=locations:
Use Cases
- Local business lookup: Retrieve full details (hours, contact, address) for POIs surfaced in web search
- Restaurant discovery pipeline: Search for restaurants, fetch POI details, filter by cuisine/rating/price_range
- Business hours checker: Get opening_hours for a business to determine if currently open
- Location-aware application: Combine with location headers to get distance calculations for nearby POIs
Notes
- ID format: Opaque strings (use
--data-urlencodefor cURL) - Units:
metricorimperialfor distance measurement preference - Max IDs: Up to 20 IDs per request

