canonical: https://jentic.com/apis/bestbuy.com/bestbuy

# Best Buy API

Jentic publishes the only available OpenAPI specification for Best Buy API, keeping it validated and agent-ready. The Best Buy Developer API provides read-only access to the retailer's product catalog, store locations, categories, recommendations such as also-viewed and trending, and open-box inventory listings. It is used for price comparison engines, retail availability checks, and product detail enrichment in shopping or research applications. The spec covers 15 endpoints across products, stores, categories, recommendations, and open-box.

## For AI agents

Search the Best Buy product catalog, look up store locations, retrieve recommendations, and check open-box availability. Read-only across 15 endpoints.

## Scope

Does not handle order placement, cart management, or payments - use for read-only Best Buy product, store, category, recommendation, and open-box data only.

## Capabilities

- Search the Best Buy product catalog by SKU, keyword, or category
- Look up Best Buy store locations and the inventory available at a store
- Retrieve product recommendations such as also-viewed and trending products
- Browse the Best Buy category tree and category detail pages
- Check open-box inventory and pricing for a specific SKU
- Pull warranty options available for a given product

## Use cases

### Retail Price Comparison

Pull product price, availability, and SKU detail from Best Buy into a price comparison engine or shopping assistant. The /v1/products endpoint supports keyword and SKU lookups and returns regular and sale prices for tens of thousands of items. A baseline integration that ingests pricing for a watchlist of SKUs takes about a day, including caching for the API key quota.

Example prompt: GET /v1/products with a keyword filter, then for each result GET /v1/products/{sku}.json and emit the regularPrice and salePrice fields

### Store Inventory Locator

Help shoppers find a nearby Best Buy that has a SKU in stock by combining /v1/products/{sku}/stores.json with /v1/stores filtered by zip code. The store endpoint returns address, phone, and operating hours for retail decision support. Wiring up a store-finder feature is typically half a day of work.

Example prompt: Given a SKU and zip code, GET /v1/products/{sku}/stores.json and return the three closest stores reporting availability

### Open-Box Deal Monitoring

Track open-box pricing on watched SKUs to surface deals to a buyer or affiliate audience. /beta/products/openBox returns the catalog of open-box offers and /beta/products/{sku}/openBox returns offers for a single product with condition grades and discount percentages. A daily polling job with delta detection takes about half a day to build.

Example prompt: GET /beta/products/openBox once per hour and notify the user when a watched SKU appears with at least 20 percent discount

### AI Agent for Shopping Research

An AI agent uses Jentic to discover Best Buy operations and answer shopper questions: comparing prices, finding nearby in-stock options, or surfacing trending models. The agent searches Jentic by intent, loads the operation schema, and executes against the 15 read-only endpoints without browsing the developer reference. Through Jentic, integration takes under an hour.

Example prompt: Search Jentic for 'find best buy product price' and execute the returned operation to retrieve current price and stock for the user's SKU

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /v1/products | Search the product catalog with filters |
| GET | /v1/products/{sku}.json | Get detail for a specific SKU |
| GET | /v1/products/{sku}/stores.json | List stores carrying a SKU |
| GET | /v1/stores | List Best Buy store locations |
| GET | /v1/products/trendingViewed | Get currently trending products |
| GET | /v1/products/{sku}/alsoViewed | Recommendations for a SKU |
| GET | /beta/products/openBox | Browse open-box inventory across the catalog |
| GET | /beta/products/{sku}/openBox | Open-box offers for a specific SKU |

## Key resources

- **Products** — Search, retrieve, and inspect Best Buy products by SKU or keyword
- **Stores** — List and look up Best Buy store locations and per-store product availability
- **Categories** — Browse the Best Buy category tree and individual category detail
- **Recommendations** — Trending, most-viewed, also-viewed, also-bought, and viewed-ultimately-bought lists
- **Open Box** — Beta endpoints exposing open-box offers and per-SKU open-box inventory
- **Warranties** — Warranty options associated with a given product SKU

## Why Jentic

- **Setup:** Wiring the Best Buy API by hand means appending your apiKey as a query parameter, learning the product, store, and open-box endpoints, and threading skus through the recommendation and stock lookups yourself. Through Jentic you install once, import the Best Buy API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Best Buy is read-only and carries its sku in the URL path (/v1/products/{sku}.json), so scope the agent to the operations it needs, such as looking up a product or finding open-box deals. You choose that operation set, and there are no write operations to add.
- **Credential handling:** Your Best Buy API key is stored once, encrypted, by your own Jentic One instance and appended as the apiKey query parameter at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'find a product price at Best Buy' or 'find open box deals', and Jentic returns the matching Best Buy operation with its parameter schema so the agent calls the right endpoint without browsing the developer portal.

## Related APIs

- **Walmart API** — Walmart product, store, and pricing data for cross-retailer comparison
- **eBay API** — eBay listings as an alternative consumer electronics inventory source
- **Shopify Admin API** — Pair retail catalog data from Best Buy with a Shopify storefront for affiliate or comparison shopping

## FAQ

### Why is there no official OpenAPI spec for Best Buy API?

Best Buy does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Best Buy API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Best Buy API use?

The Best Buy API uses an API key passed as the apiKey query string parameter on every request. Keys are issued through the Best Buy developer portal. When called via Jentic, the key is stored encrypted in your Jentic One instance and appended to outgoing requests at execution time so it never appears in the agent context.

### Can I check open-box availability for a specific SKU?

Yes. GET /beta/products/{sku}/openBox returns open-box offers for a SKU including condition grade and discount, while GET /beta/products/openBox returns the catalog-wide open-box feed. These endpoints are flagged beta in the spec, so expect occasional schema changes.

### How do I look up a product price through Jentic?

Run pip install jentic and search for 'best buy product price'. Jentic returns GET /v1/products/{sku}.json, the agent loads the schema, and executes with the SKU. Combine with /v1/products/{sku}/stores.json to also surface in-store availability.

### What rate limits apply to the Best Buy API?

Best Buy enforces per-key call quotas that vary by partner tier and endpoint, with daily and per-second caps documented on the developer portal. The OpenAPI spec does not encode these explicitly, so cache catalog responses and back off on 429 to stay within the quota.

### Is the Best Buy API free?

The Best Buy Developer API is free for approved partners but requires an API key obtained through the Best Buy developer programme. There is no charge per request within the issued quota; commercial use cases must be approved by Best Buy before launch.

### Can I limit what my agent is allowed to do with the Best Buy API?

Yes. Because you run Jentic One yourself, your own rules decide exactly which Best Buy operations the agent may call, so you can scope it to just the read-only endpoints it needs, such as looking up a product by SKU with GET /v1/products/{sku}.json or checking open-box deals with GET /beta/products/{sku}/openBox. The Best Buy API is read-only and carries its SKU in the URL path, so there are no write operations to worry about, and the agent can only invoke the operation set you approve. Your API key is held by your own instance and appended at execution time, so the agent never sees it.