Get a Yelp business · Yelp API
Returns a Yelp business by alias: rating, review count, price range, phone, website, address, coordinates, categories, opening hours and amenities. Returns `not_found` when the business does not exist.
Using ChatGPT, Claude Code or another client? See the setup steps
curl https://api.unifapi.com/yelp/businesses/{id} \
-H "Authorization: Bearer $UNIFAPI_KEY"Parameters
- idpathrequired
- Yelp business alias, as in yelp.com/biz/{id}.
- The parameter for this Yelp operation. Use the URL-visible slug or id described in the docs.
This operation is part of the Yelp API in the local & maps category. It uses the same Bearer token, request tracing, error model, and billing envelope as every UnifAPI endpoint, so agents can switch between platforms without custom per-vendor glue code.
Use it when a workflow needs Yelp public data alongside other maps and local-business sources, but should still keep one API key, one account balance, and one predictable JSON contract.
Common agent workflows
- Look up public Yelp data for agents that need reliable open-web context.
- Give an AI agent a stable Yelp data source without building a per-platform integration.
- Normalize Yelp responses into the same UnifAPI envelope used across the catalog.
Unified envelope, platform-native fields
- Lookup responses return one canonical object in `data` with stable identifiers, source URLs where available, and platform-specific metadata normalized into predictable JSON.
- The operation has a 6 credits ($0.006) minimum charge, so `billing.records_charged` can be higher than the visible records returned.
- A not-found or invalid-input condition uses the unified UnifAPI error shape, so callers do not need special handling for each source platform.
Response status codes
Billing
This operation charges 1 credit per billable record, with a 6 credits ($0.006) operation minimum. Public responses include billing metadata with credits charged, records charged, and remaining workspace balance. Incorrect Credit deductions caused by platform failures can be restored as billing corrections.
Errors and retries
Authentication, validation, rate-limit, not-found, and provider errors use the unified UnifAPI error format. Agents should log `request_id`, retry only retryable failures, and treat invalid API keys, disabled keys, and expired keys as the same public `unauthorized` error type.
Fields in the data object
A successful Get a Yelp business call returns one data object with these fields (12 of 16 shown — the docs list the full schema).
- aliasstring | null
- Business alias from its Yelp URL.
- business_idstring | null
- namestring | null
- urlstring | null
- ratingnumber | null
- review_countnumber | null
- is_claimedboolean | null
- is_closedboolean | null
- price_rangestring | null
- phonestring | null
- websitestring | null
- addressobject | null
More Yelp operations
Combine endpoints from the same platform, then join the results with other UnifAPI categories without changing authentication or response parsing.
List photos of a Yelp business
Returns public photos of a Yelp business with captions and URLs. Paginate with `cursor`.
List reviews of a Yelp business
Returns public reviews of a Yelp business with rating, text, author, photos and owner replies. Choose recommended, not-recommended or removed reviews with `category`. Paginate with `cursor`.
Search Yelp businesses
Searches Yelp for businesses by name, service or category near a location, sorted by Yelp's recommendation, rating or review count. Paginate with `cursor`.