Digi-Key vs Rappi

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.

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.