Catalog

Yelp API

Yelp data through one normalized API - per-request USD pricing, no subscriptions, and automatic failover on redundant endpoints.

Endpoints1Providers2From · search$3.50/1k req · IbexFull breakdownRead docs
Uptime
100.00%
30d · 6 calls
Requests
6
30d · weekly, last 12 wks
Response
5.7s
median · 30d
POST

Search

Most used
/v1/run/yelp.searchyelp.search
Search Yelp for businesses by keyword and location: up to 20 listings with ratings, categories, and core business info per request.
6 /mo
â–²400%
100.00%
5730ms p50
2
from$3.50/1k req
Ibex

About the Yelp API

Every provider prices each endpoint independently, so the table shows the cheapest per endpoint. Open one to compare all providers.

Measured performance

What the Yelp API actually does

Every call through AnyAPI over the last 30 days, counted here rather than promised.

100.0%
of calls succeeded (6 calls)
Succeeded on first lane 100.0%
Response time (6 calls)
Typical (p50)
5.7s
Half of requests finish within 5.7s
p99 response time
13.8s
p99 response time: 99% of requests finish within 13.8s

FAQ

About the Yelp API

The AnyAPI Yelp API returns Yelp data as normalized JSON across 1 endpoint: search. You call one endpoint per job with a single key, and AnyAPI routes each request across 2 sources, falling back automatically when one fails. Pricing is in US dollars, from $3.50 per 1,000 requests, with no subscription and no monthly minimum. Over the last 30 days, 100.0% of Yelp calls through AnyAPI succeeded, with a median response time of 5.7 seconds across 6 measured calls.

Pricing is in US dollars, from $3.50 per 1,000 requests, with no subscription and no monthly minimum. You fund one USD wallet, each call draws it down, and a failed request costs $0.

One endpoint: search. Every one takes the same authentication and returns the same normalized response shape, so reaching a second Yelp endpoint is a change of URL and nothing else.

Over the last 30 days, 100.0% of Yelp calls through AnyAPI succeeded, with a median response time of 5.7 seconds across 6 measured calls. These are AnyAPI's own measurements of traffic through the gateway, recomputed continuously, not a published service-level target.