I’ve been working with the (search.api.brave.com/app/documentation/web-search/get-started), but I’m having issues retrieving detailed location data using the /local/pois endpoint. Some location IDs returned from the web search query don’t provide results when used with the POI endpoint, even though they appear valid in the initial query.
Here’s an example of my request:
curl -s --compressed "https://api.search.brave.com/res/v1/local/pois?ids=1520066f3f39496780c5931d9f7b26a6&ids=invalid_id" \
-H "accept: application/json" \
-H "Accept-Encoding: gzip" \
-H "x-subscription-token: <YOUR_API_KEY>"
Additionally, when I try fetching AI-generated descriptions using /local/descriptions, I sometimes get empty responses even for valid IDs:
curl -s --compressed "https://api.search.brave.com/res/v1/local/descriptions?ids=1520066f3f39496780c5931d9f7b26a6" \
-H "accept: application/json" \
-H "Accept-Encoding: gzip" \
-H "x-subscription-token: <YOUR_API_KEY>"
Questions:
- Why are some valid IDs not returning results on these endpoints?
- Is there a specific limitation or dependency between these endpoints?
- Could there be an issue with rate-limiting or the way data is cached?
Any help troubleshooting this would be appreciated!