canonical: https://jentic.com/apis/rappi.com/rappi

# Rappi Restaurant Integrations API

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.

## For AI agents

Programmatically create or update a menu, list menus. Covers 34 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- 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

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'create or update a menu', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| 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 |

## Key resources

- **Availability** — Operations related to Availability
- **Menu** — Operations related to Menu
- **Orders** — Operations related to Orders
- **Scheduling** — Operations related to Scheduling
- **Stores** — Operations related to Stores

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 66 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 99 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 50 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 63 / 100
- **View full report:** https://jentic.com/apis/rappi.com/rappi/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Rappi Restaurant Integrations API by hand means learning its bearer auth and hand-coding requests across its menu and order endpoints. Through Jentic you install once, import the Rappi Restaurant Integrations API from the API Directory, store the bearer token once, and your agent calls it.
- **Permission scoping:** Rappi puts the store and order ids in the URL path (`/menu/approved/{storeId}`, `/orders/{orderId}/take/{cookingTime}`), so a rule can pin your agent to one store: it can read menus and orders for that store and nothing else. You choose the operations it may call, so ones like rejecting an order are not included unless you add them.
- **Credential handling:** Your Rappi bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get pending orders' or 'update a store menu', and Jentic returns the matching Rappi operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### 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 your Jentic One instance 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 through Jentic One, the self-hosted execution layer, 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.

### Can I limit what my agent is allowed to do with the Rappi Restaurant Integrations API?

Yes. Because Rappi puts the store and order ids in the URL path (for example `/menu/approved/{storeId}` and `/orders/{orderId}/take/{cookingTime}`), a rule in your self-hosted Jentic One can pin the agent to a single store so it only reads menus and orders for that store. You decide which operations the agent may call, so a sensitive action like rejecting an order (PUT `/orders/{orderId}/reject`) is not available unless you add it. Since Jentic One runs under your own control, your rules and the Rappi bearer token you store there govern exactly which endpoints and credentials the agent can use.