Yelp APIFetch a Yelp business and its customer reviews as structured JSON with one SocialCrawl API key. Shared place and review schema. Reads are priced in credits.
2 active endpoints. Business info then reviews.
Two live read endpoints for Yelp. Look up a business by its encid, then page reviews 10 at a time. No search on this surface. Alias slugs are not found.
/v1/yelp/business/infoOne Yelp business by 22-character encid. Name, unrounded rating, exact review count, price level, address, coordinates, categories, photos, timezone. Alias URLs return 404 and are not billed. Standard tier (1 credit).
id or url
/v1/yelp/business/reviewsCustomer reviews for that encid. 10 per page with a cursor, owner replies, photos, language, and HELPFUL votes. Page 2 does not overlap page 1. Advanced tier (5 credits).
id or url, cursor
Returns one Yelp business by its 22-character encid: name, unrounded rating, review count, price level, address, coordinates, categories, photos, and timezone.
Use it when you already have a Yelp encid. Alias slugs return not found. There is no search on this surface.
1 credit
$ curl https://www.socialcrawl.dev/v1/yelp/business/info?id=zj8Lq1T8KIC5zwFief15jg \
-H "x-api-key: sc_YOUR_API_KEY"// No example response recorded for this endpoint yet. The endpoint docs cover the response shape and every fieldYelp is a normal SocialCrawl data surface. You call GET /v1/yelp/… with an API key, spend credits on live misses, and get a single JSON envelope back.
Send your key in the x-api-key header. No Yelp OAuth app for public reads. The same key works across SocialCrawl platforms.
Both Yelp routes are GET. Pass id (the encid) or a /biz/{encid} URL. cursor pages reviews. We validate formats before charging.
business/info costs 1 credit. business/reviews costs 5 credits. Cache hits cost 0. Empty or hard failures refund.
Every response is the same shape: success, data, credits_used, credits_remaining, request_id, cached. Review lists carry next_cursor when another page exists.
You already hold a Yelp encid. Look the business up, then page reviews.
GET /v1/yelp/business/info?id=…Place with rating, address, coordinates, photos
Confirms the encid before you spend on reviews.
GET /v1/yelp/business/reviews?id=…ReviewList of 10 reviews
Customer language plus owner replies.
GET /v1/yelp/business/reviews?id=…&cursor=…The next 10 reviews, no overlap
cursor from the previous page.
GET /v1/yelp/business/info?id=zj8Lq1T8KIC5zwFief15jg
Host: www.socialcrawl.dev
x-api-key: sc_your_api_key_here
GET /v1/yelp/business/reviews?id=zj8Lq1T8KIC5zwFief15jg{
"success": true,
"data": {
"place": {
"id": "zj8Lq1T8KIC5zwFief15jg",
"name": "Prince Street Pizza",
"rating": { "value": 4.3, "max": 5 },
"reviews_count": 5712
}
},
"credits_used": 1,
"credits_remaining": 9999,
"request_id": "req_…",
"cached": false
}Field names match the rest of SocialCrawl where archetypes align. Parse once, reuse across platforms.
id, name, url, rating, reviews_count, price_level, address, coordinates, categories, photos
items[] with text, rating, author, responses[], images, published_at
next_cursor, 10 new ids, zero overlap
Same request lifecycle as every other /v1 platform endpoint. Yelp is not a sidecar.
Next.js catch-all routes into the Hono social API. We mint a request_id, authenticate the key, then enforce rate limit (600/min) and concurrency (50 in flight per key).
Registry lookup finds yelp/business/info (or business/reviews). Required params and format checks run first. Invalid input returns 400 with no charge. Valid calls debit the tier cost atomically before upstream work.
A deterministic cache key is built from platform + resource + params. Hit: return immediately, credits_used = 0. Miss: we fetch, retry on 5xx/network, and trip a circuit breaker if the source is unhealthy.
Upstream JSON is mapped to Place and ReviewList, validated against the canonical Zod schema, then wrapped in the success envelope and logged for billing audit.
Billing rules that matter in production
Yelp is public read data. We normalize it into the SocialCrawl schema so your code does not learn a second vendor SDK.
Public business profiles and customer reviews about a local business. Not a keyword search.
Business and review reads run as ordinary GETs. Identity is the 22-character encid.
Place for the business and ReviewList for its reviews.
No search, nearby, menus, or Q&A. Alias slugs are not found.
The jobs this API is most often used for.
Local-business reputation and review mining
Callers hold an encid, confirm the place, then page reviews. Yelp Place plus ReviewList on the same schema as Tripadvisor, keyed by encid, with a 5-credit review page after a 1-credit lookup.
Live misses are typically under two seconds for info and a few seconds for a review page.
Common ways teams put this data to work, and the stack each one tends to run.
business/info for rating and review count, reviews for recent language.
page reviews with cursor and keep owner replies.
same Place schema as Tripadvisor for a restaurant set.
Info is 1 credit. Reviews are 5. Cache hits are free.
curl "https://www.socialcrawl.dev/v1/yelp/business/info?id=zj8Lq1T8KIC5zwFief15jg" \
-H "x-api-key: sc_your_api_key_here"curl "https://www.socialcrawl.dev/v1/yelp/business/reviews?id=zj8Lq1T8KIC5zwFief15jg" \
-H "x-api-key: sc_your_api_key_here"Same key as the rest of the catalog
Every endpoint returns structured JSON in a unified envelope. Computed fields such as engagement rate and content category are included only where the endpoint supports them and the required source inputs are present.
Find answers to frequently asked questions about SocialCrawl's API, pricing, and capabilities.
Contact us