Catalog

Best Buy API

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

Endpoints3Providers2From · product$0.85/1k req · BadgerFull breakdownRead docs
Uptime
60.00%
30d · 5 calls
Requests
5
30d
Response
2.7s
median · 30d

Measured performance

What the Best Buy API actually does

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

60.0%
of calls succeeded (5 calls)
Succeeded on first lane 60.0%Failed 40.0%
Response time estimate (3 calls across endpoints)
Weighted p50 estimate
2.7s
Request-weighted average of endpoint p50 values, not a combined request percentile
Weighted p99 estimate
2.7s
Request-weighted average of endpoint p99 values, not a combined request percentile

FAQ

About the Best Buy API

The AnyAPI Best Buy API returns Best Buy data as normalized JSON across 3 endpoints: product, reviews, and 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 $0.85 per 1,000 requests on the cheapest endpoint, with no subscription and no monthly minimum. Over the last 30 days, 60.0% of Best Buy calls through AnyAPI succeeded, with a request-weighted median response time of 2.7 seconds across 5 measured calls.

Pricing is in US dollars, from $0.85 per 1,000 requests on the cheapest endpoint, with no subscription and no monthly minimum. You fund one USD wallet and each call draws it down. Some failed wallet-funded requests incur processing charges that we pass through at cost, with no markup; the error response shows the amount charged.

3 endpoints: product, reviews, and search. Every one takes the same authentication and returns the same normalized response shape, so reaching a second Best Buy endpoint is a change of URL and nothing else.

Over the last 30 days, 60.0% of Best Buy calls through AnyAPI succeeded, with a request-weighted median response time of 2.7 seconds across 5 measured calls. These are AnyAPI's own measurements of traffic through the gateway, recomputed continuously, not a published service-level target.