Shopping · head-to-head
Best Buy vs Digi-Key
Best Buy's public REST API exposes product, store, category, and recommendation data behind a free API key registered through its developer portal. Responses can be returned as either JSON or XML for most endpoints, though the newer Recommendations endpoints are JSON-only. Live probing shows the gateway actively validates keys server-side but returns no CORS headers, so it is built for server-side integration rather than direct browser calls.
Digi-Key's api.digikey.com gateway runs a genuine OAuth2 flow: its authorization endpoint rejects requests missing a client_id, and resource endpoints additionally require a client-specific header, ruling out simple API-key auth. Access to product, ordering, and barcode data is free with per-product rate limits, and CORS is explicitly configured, echoing the request Origin on both live calls and OPTIONS preflights.
| Best Buy | Digi-Key | |
|---|---|---|
| Authentication | API Key | OAuth |
| Pricing | free | free |
| Formats | JSON, XML | JSON |
| CORS | no | yes |
| HTTPS | Yes | Yes |
Digi-Key supports CORS, while Best Buy doesn't — pick Digi-Key for direct browser calls.