Retrieve a Yelp business profile
View all Yelp Business, Reviews & Restaurant Data endpoints →Get the profile of one known Yelp business using the required business query parameter. It accepts a business alias, a 22-character business ID or a yelp.com business URL. Select the intended branch before attaching its profile to your own records. An observed successful response was a business object containing id, alias, name, rating and review_count, along with address and contact data, hours, amenities and popular_dishes. The tested Gary Danko profile returned rating 4.5 and review_count 6148; those are sample observations, not fixed values or a freshness guarantee. The catalog also describes phone, website and health-score information, but health-score availability was not established by the observed response summary. The supplied source example additionally includes about, alternate_links and alternate_names. Its visible about fields include history, owner, specialties and year_established; visible address fields include city, country_code, formatted, line1, line2, line3, postal_code and state. The example also shows amenities entries with name and is_available. Those example-specific structures are not independently verified by the probe summary, and the example is incomplete. Do not treat omitted attributes as false or unavailable. A deliberately nonexistent business returned HTTP 404 with an error field, so callers must handle not-found responses separately from a successful profile.
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/business-details API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/yelp/business-details?key=<API_KEY>&business=gary-danko-san-francisco'
Query Result
Use Cases
- Enrich a confirmed restaurant branch with contact information, opening hours and amenities while leaving any unreturned service attributes unknown.
- Build a directory profile card that preserves the observed id and alias alongside rating and review_count, adding an application-side fetch timestamp for later refresh decisions.
- Cross-check an existing store record against the returned address and contact data before joining that branch to separately retrieved reviews or photos.
- Route HTTP 404 business lookups into an identifier-correction queue rather than storing an empty profile as a valid business record.
- Prototype a venue-information panel with popular_dishes and optional business background, rendering only the attributes actually returned for that venue.
Frequently asked questions
Which identifiers does the business parameter accept?
It accepts a Yelp business alias, a 22-character business ID or a yelp.com business URL. The required query value identifies one business, not a comma-separated batch.
Which business profile fields were actually observed?
The successful observation contained id, alias, name, rating, review_count, address and contact data, hours, amenities and popular_dishes. It was one business profile and does not establish that every business returns all of those attributes.
Are health scores and background information guaranteed?
No. Health scores are catalog-described, while about, alternate_links and alternate_names appear in the incomplete source example. The observed response summary does not independently establish those fields or universal availability.
What happens when the business does not exist?
The negative test returned HTTP 404 with an error field describing a business-not-found condition. Handle that non-success response separately; do not interpret it as a successful profile with no attributes.
Are the example rating and review count current values for every call?
No. Rating 4.5 and review_count 6148 belonged to the tested Gary Danko response. They are sample observations only; the supplied evidence does not establish update frequency or real-time accuracy.
Does a missing amenity mean the business does not offer it?
Not necessarily. Preserve the distinction between a returned availability value and an omitted attribute. The source example shows amenity name and is_available fields, but missing data alone does not prove a service is unavailable.