Inspect Yelp Search Filter Options
View all Yelp Business, Reviews & Restaurant Data endpoints →Inspect the filter options documented for a Yelp search context. location is required and accepts a city, neighborhood, address or ZIP code; its documented default is Austin, TX. Optionally supply query for a search term and category for a Yelp category alias, category name or Yelp search URL containing cflt=. The documented filter groups cover price, features, categories, distance and service types. This operation has no recorded nonempty response, and its supplied response example is an empty object. Exact response field names, option identifiers, grouping structure and availability of individual filters are therefore unverified. This endpoint describes filter availability; it does not execute a filtered business search. The main business-search operation is not included in this project, and quick search does not accept these filter options.
API Features
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/yelp/search-filters API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/yelp/search-filters?key=<API_KEY>&location=Austin%2C+TX'
Query Result
Use Cases
- Audit the documented price, distance and service filter capabilities for a local-search product design without promising executable filters.
- Create a query-and-location fixture that retains the context of returned filter labels for later compatibility checks once the response structure is confirmed.
- Review whether a proposed category-specific interface has evidence for each displayed filter group before enabling any controls.
- Document a search-integration boundary: expose filter inspection separately and keep filtered execution disabled because quick search does not accept these options.
Frequently asked questions
Which inputs define the filter context?
location is required. query and category are optional strings that can further describe the search context. The documented default location is Austin, TX.
What can I send in category?
The documentation accepts a Yelp category alias such as pizza or italian, a category name such as Coffee & Tea, or a Yelp search URL containing cflt=. No fixed category enum is supplied.
Which filter groups are documented?
Price, features, categories, distance and service types are listed. No nonempty response was recorded for this operation, so the evidence does not confirm the exact groups or options returned for a particular context.
Are the response keys and option values verified?
No. The supplied response example is an empty object, and there is no recorded nonempty response for this operation. Property names, option identifiers and grouping structure must be confirmed before building a response parser.
Does this endpoint return filtered businesses?
No filtered business-result response is documented here. This operation is for inspecting filter options, not executing a filtered business search.
Can I apply these options to quick search?
No. Quick search accepts only limit, location and query; it does not accept category, price, distance, feature or service-type filters. The main business-search operation is not included in this project.