Rappi Restaurant Integrations API
✓ Official Vendor SpecDeveloper ToolsSource Controlbearer34 EndpointsREST
For Agents
Programmatically create or update a menu, list menus. Covers 34 operations with bearer authentication.
Use for: I need to or update a menu, I want to menus, Search for menu approval status, Find all latest menu for store
Not supported: Does not handle payments, communications, or crm — use for developer tools only.
Rappi's public API for restaurant integrations. Allows partners to manage menus, orders, stores, availability, webhooks, and scheduling for their restaurant operations on the Rappi platform. The API exposes 34 endpoints secured with bearer authentication.
Install Jentic One Beta
Connect the Rappi Restaurant Integrations API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Rappi Restaurant Integrations API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Rappi Restaurant Integrations API.
Create or update a menu
List menus
Get menu approval status
Take an order
Access Rappi Restaurant Integrations API developer tools resources via REST API
Use Cases
Patterns agents use Rappi Restaurant Integrations API for, with concrete tasks.
★ Developer Tools Operations
Use the Rappi Restaurant Integrations API to perform developer tools operations programmatically. The API provides 34 endpoints covering core functionality including create or update a menu, list menus, get menu approval status.
Call POST /menu to create or update a menu
Automated Availability Management
Automate availability operations by combining multiple Rappi Restaurant Integrations API endpoints. Agents can list menus and then get menu approval status in a single workflow.
Call GET /menu to list menus, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Rappi Restaurant Integrations API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.
Search Jentic for 'create or update a menu', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
34 endpoints — rappi's public api for restaurant integrations.
METHOD
PATH
DESCRIPTION
POST
/menu
Create or update a menu
GET
/menu
List menus
GET
/menu/approved/{storeId}
Get menu approval status
GET
/menu/rappi/{storeId}
Get latest menu for store
GET
/orders
List new orders
GET
/orders/status/sent
List orders in SENT status
PUT
/orders/{orderId}/take/{cookingTime}
Take an order
PUT
/orders/{orderId}/reject
Reject an order
POST
/menu
Create or update a menu
GET
/menu
List menus
GET
/menu/approved/{storeId}
Get menu approval status
GET
/menu/rappi/{storeId}
Get latest menu for store
GET
/orders
List new orders
GET
/orders/status/sent
List orders in SENT status
PUT
/orders/{orderId}/take/{cookingTime}
Take an order
PUT
/orders/{orderId}/reject
Reject an order
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Rappi Restaurant Integrations API bearer credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'create or update a menu') and Jentic returns the matching Rappi Restaurant Integrations API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Rappi Restaurant Integrations API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
FAQs
Specific to using Rappi Restaurant Integrations API through Jentic.
What authentication does the Rappi Restaurant Integrations API use?
The Rappi Restaurant Integrations API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.
Can I create or update a menu with the Rappi Restaurant Integrations API?
Yes. Use the POST /menu endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Rappi Restaurant Integrations API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I create or update a menu through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'create or update a menu'. Jentic returns the matching Rappi Restaurant Integrations API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the Rappi Restaurant Integrations API have?
The Rappi Restaurant Integrations API exposes 34 endpoints covering availability, menu, orders operations.
GET STARTED