Shopping · head-to-head
eBay vs Rappi
eBay's REST platform — Browse, Sell, and related APIs — requires an OAuth2 client-credentials or authorization-code token, confirmed live by a standard invalid_client error from its token endpoint, and is built for server-side integration rather than in-browser calls. New developer accounts get a free daily call allowance with no published paid tier, and higher volume comes from an approval process rather than a fee.
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.
| eBay | Rappi | |
|---|---|---|
| Authentication | OAuth | OAuth |
| Pricing | free | free |
| Formats | JSON, XML | JSON |
| CORS | no | yes |
| HTTPS | Yes | Yes |
Rappi supports CORS, while eBay doesn't — pick Rappi for direct browser calls.