Rappi

Rappi Partners REST API

The Rappi Partners REST API is the integration surface used by approved restaurants, grocery and retail merchants, and middleware/POS providers to operate on the Rappi marketplace. Authentication is OAuth 2.0 client-credentials — partners receive a client_id and client_secret from Rappi after manual onboarding, exchange them at POST token/login/integrations for a bearer access token, and re-issue the token at least weekly. The API exposes endpoints for menu and catalog management, product and store availability toggling, retrieving store data, accepting and progressing user orders, and a separate Financial surface for reconciliation. A parallel "Rests API" track covers the same operations for the restaurant vertical. Webhook events deliver order lifecycle and store updates to partner-hosted callback URLs. Rappi enforces a 45-second minimum gap between requests and expects integrators to maintain a 98% API success rate; production access is gated on certification by the Rappi integrations team.

Rappi Partners REST API is published by Rappi on the APIs.io network.

Tagged areas include Orders, Menus, Catalog, Availability, and Stores. The published artifact set on APIs.io includes API documentation, an API reference, a getting-started guide, and authentication docs.

GitHub

Documentation

📖
Documentation
https://dev-portal.rappi.com/
📖
APIReference
https://dev-portal.rappi.com/en/api-reference/
📖
GettingStarted
https://dev-portal.rappi.com/en/api-reference/
📖
Authentication
https://dev-portal.rappi.com/en/api-reference/authentication/

Other Resources

🔗
Webhooks
https://dev-portal.rappi.com/en/api-reference/webhooks/

API entry from apis.yml

apis.yml Raw ↑ 
aid: rappi:partners-api
name: Rappi Partners REST API
description: The Rappi Partners REST API is the integration surface used by approved restaurants, grocery
  and retail merchants, and middleware/POS providers to operate on the Rappi marketplace. Authentication
  is OAuth 2.0 client-credentials — partners receive a client_id and client_secret from Rappi after manual
  onboarding, exchange them at POST token/login/integrations for a bearer access token, and re-issue the
  token at least weekly. The API exposes endpoints for menu and catalog management, product and store
  availability toggling, retrieving store data, accepting and progressing user orders, and a separate
  Financial surface for reconciliation. A parallel "Rests API" track covers the same operations for the
  restaurant vertical. Webhook events deliver order lifecycle and store updates to partner-hosted callback
  URLs. Rappi enforces a 45-second minimum gap between requests and expects integrators to maintain a
  98% API success rate; production access is gated on certification by the Rappi integrations team.
image: https://kinlane-productions.s3.amazonaws.com/apis-json/apis-json-logo.jpg
humanURL: https://dev-portal.rappi.com/
tags:
- Orders
- Menus
- Catalog
- Availability
- Stores
- Webhooks
- Financial
- OAuth
- REST
properties:
- type: Documentation
  url: https://dev-portal.rappi.com/
- type: APIReference
  url: https://dev-portal.rappi.com/en/api-reference/
- type: GettingStarted
  url: https://dev-portal.rappi.com/en/api-reference/
- type: Authentication
  url: https://dev-portal.rappi.com/en/api-reference/authentication/
- type: Webhooks
  url: https://dev-portal.rappi.com/en/api-reference/webhooks/