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.