Look up up to 20 known Yelp businesses
View all Yelp Business, Reviews & Restaurant Data endpoints →Retrieve compact information for a supplied list of known Yelp businesses. The required businesses query parameter is one comma-separated string containing up to 20 business aliases, IDs or yelp.com URLs. This is identifier-based enrichment, not a location or city-wide discovery search. The catalog documents rating, phone, website, address, coordinates and photo as returned information. These are documented output concepts, not confirmed JSON field names: no batch response was observed, and the supplied source response example is an empty object. The response envelope, record ordering, representation of unresolved inputs and partial-failure behavior remain unverified. Confirm those details before relying on positional matching in a production import.
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/batch-business-lookup API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/yelp/batch-business-lookup?key=<API_KEY>&businesses=gary-danko-san-francisco%2Ctonys-pizza-napoletana-san-francisco'
Query Result
Use Cases
- Refresh a CRM list of already-resolved Yelp references in groups of up to 20, checking the returned structure before merging individual business records.
- Compare catalog-described phone, website, address and coordinates against an internal branch master to flag records that need a detailed profile lookup.
- Prepare a compact business-comparison dataset for a known shortlist without presenting the lookup as an exhaustive city-wide prospect search.
- Design an enrichment import that retains each submitted reference and reconciles unresolved entries only after confirming actual batch response matching.
Frequently asked questions
What should I put in the businesses parameter?
Send one comma-separated string of known Yelp business aliases, IDs or yelp.com URLs. The documented limit is 20 references per request; this parameter is a string, not a JSON array.
Can this endpoint discover every business in a city?
No. It accepts already-known business references and does not expose a location, category or city-wide discovery input.
Which output fields are documented, and which were observed?
The catalog describes rating, phone, website, address, coordinates and photo information. No batch response was observed, and the supplied source example is an empty object, so exact JSON keys and the response envelope are unverified.
Can I match results to inputs by their array position?
Do not assume positional matching. Result ordering, unresolved-reference representation and partial-failure handling are not established by the supplied evidence; verify them before updating your own records.