By Search Term Endpoint
This endpoint finds places that match a string
The find
endpoint allows you to search for specific venues by name or partial name matches. This is perfect for when users know exactly what they're looking for or want to find a particular establishment.
Endpoint details
Caching
If you are caching the venue details, you should only cache the venue ID. Do not cache the full venue details response, as the data changes frequently and must always be fetched fresh for accuracy and compliance.
Query parameters
search term (required)
The venue name or partial name to search for. Minimum 1 character.
lat (optional)
Latitude coordinate to centre the search around. If provided, results are ordered by proximity.
lon (optional)
Longitude coordinate to centre the search around. Must be provided with lat.
location (optional)
Human-readable location string (e.g., "London", "New York") for broader area searches.
maxDistanceMeters (optional)
Maximum search distance in meters. Defaults to 5,000m (5km).
Basic usage
Request examples
Response format
Search strategies
Exact name matching
Use the full, exact name for precise results:
Partial name matching
Use partial names to find similar venues:
Generic term search
If you are searching for a specific type of establishment, you should use the search
endpoint and set the genre
to your desired genre. If you use the find
endpoint below, you will get results with 'Coffee' in the name.
Real-world examples
Best practice
- Use meaningful search terms: "The Leaky Cauldron" is better than "The"
- Provide coordinates when possible: Results are more relevant and ordered by proximity
- Set appropriate distance limits: Don't search 5km unless necessary
- Handle partial matches: Users often type partial names
API Reference
Below is the complete OpenAPI specification for the search term endpoint: