Shopping · head-to-head
Best Buy vs Rappi
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.
Rappi's public API lets approved merchant partners manage store menus and orders across its Latin American on-demand delivery platform. Access requires a formal partnership and uses OAuth2 — Authorization Code with PKCE for partner-facing flows, plus Auth0-issued bearer tokens for machine-to-machine calls — confirmed live against its login/token gateway. Each country Rappi operates in runs its own regional API host.
| Best Buy | Rappi | |
|---|---|---|
| Authentication | API Key | OAuth |
| Pricing | free | free |
| Formats | JSON, XML | JSON |
| CORS | no | yes |
| HTTPS | Yes | Yes |
Rappi supports CORS, while Best Buy doesn't — pick Rappi for direct browser calls.