Rappi vs WooCommerce

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.

WooCommerce's REST API isn't a centrally hosted service — every self-hosted WooCommerce store exposes its own instance, authenticated by a consumer key/secret pair sent as HTTP Basic Auth credentials over HTTPS, per WooCommerce's own documentation. Because CORS support depends entirely on each merchant's own server configuration rather than the protocol itself, it can't be verified as a single blanket property of "the API." The protocol ships free with the open-source plugin; the only cost is whatever the merchant already pays to host their own store.