Rappi Python API Docs | dltHub

Build a Rappi-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.

Last updated:

Rappi's REST API documentation is available at https://dev-portal.rappi.com/en/api-reference/rests-api/. API requests must specify the country domain, e.g., https://api.rappi.com.mx. Authentication requires a token with the audience {Country domain}/api/v2/restaurants-integrations-public-api. The REST API base URL is https://{COUNTRY_DOMAIN} and All requests require a Bearer access token sent in the x-authorization header..

dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv pip install "dlt[workspace]" and start loading Rappi data in under 10 minutes.


What data can I load from Rappi?

Here are some of the endpoints you can load from Rappi:

ResourceEndpointMethodData selectorDescription
orders/api/v2/restaurants-integrations-public-api/ordersGETorder_detailReturns the collection of new orders for the authenticated ally.
orders_status_sent/api/v2/restaurants-integrations-public-api/orders/status/sentGETorder_detailReturns orders in SENT status.
order_events/api/v2/restaurants-integrations-public-api/orders/{orderId}/eventsGETeventsReturns latest events for a given order.
menu/api/v2/restaurants-integrations-public-api/menuGETReturns menus created by the authenticating ally.
menu_by_store/api/v2/restaurants-integrations-public-api/menu/rappi/{storeId}GETmenuReturns last menu created for a store.
stores/api/v2/restaurants-integrations-public-api/stores-paGETReturns list of stores for authenticated client.
corridor_by_integration/api/rest-ops-utils/corridor/integration/{integrationId}GETCorridor schedules by integration id.
store_schedule/api/rest-ops-utils/store/schedule/{storeId}GETStore hours/schedule.
menu_integration/api/rest-ops-utils/menu/integration/{integrationId}GETProduct status for integration id.
auth_login_integrations/restaurants/auth/v1/token/login/integrationsPOSTtokenObtain access token for integrations.

How do I authenticate with the Rappi API?

Obtain an access token via the integrations or utils login endpoints (OAuth2). Supply the token on every request as header 'x-authorization: bearer {access_token}'. Example auth token endpoint (dev): https://api.dev.rappi.com/restaurants/auth/v1/token/login/integrations

1. Get your credentials

  1. Register as an ally/integration with Rappi support to receive client_id and client_secret. 2) Call POST /restaurants/auth/v1/token/login/integrations (or /utils/login) with JSON {"client_id":...,"client_secret":...} to obtain an access_token (valid ~1 week). 3) Use the returned token in header 'x-authorization: bearer {access_token}' for API requests.

2. Add them to .dlt/secrets.toml

[sources.rappi_source] access_token = "your_access_token_here"

dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.


How do I set up and run the pipeline?

Set up a virtual environment and install dlt:

uv venv && source .venv/bin/activate uv pip install "dlt[workspace]"

1. Install the dlt AI Workbench:

dlt ai init --agent <your-agent> # <agent>: claude | cursor | codex

This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →

2. Install the rest-api-pipeline toolkit:

dlt ai toolkit rest-api-pipeline install

This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →

3. Start LLM-assisted coding:

Use /find-source to load data from the Rappi API into DuckDB.

The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.

4. Run the pipeline:

python rappi_pipeline.py

If everything is configured correctly, you'll see output like this:

Pipeline rappi_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset rappi_data The duckdb destination used duckdb:/rappi.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

dlt pipeline rappi_pipeline show

This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.


Python pipeline example

This example loads orders and menu from the Rappi API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def rappi_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://{COUNTRY_DOMAIN}", "auth": { "type": "bearer", "token": access_token, }, }, "resources": [ {"name": "orders", "endpoint": {"path": "api/v2/restaurants-integrations-public-api/orders", "data_selector": "order_detail"}}, {"name": "menu", "endpoint": {"path": "api/v2/restaurants-integrations-public-api/menu"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="rappi_pipeline", destination="duckdb", dataset_name="rappi_data", ) load_info = pipeline.run(rappi_source()) print(load_info)

To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.


How do I query the loaded data?

Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.

Python (pandas DataFrame):

import dlt data = dlt.pipeline("rappi_pipeline").dataset() sessions_df = data.orders.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM rappi_data.orders LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("rappi_pipeline").dataset() data.orders.df().head()

See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.


What destinations can I load Rappi data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample value
DuckDB (local, default)"duckdb"
PostgreSQL"postgres"
BigQuery"bigquery"
Snowflake"snowflake"
Redshift"redshift"
Databricks"databricks"
Filesystem (S3, GCS, Azure)"filesystem"

Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.


Next steps

Continue your data engineering journey with the other toolkits of the dltHub AI Workbench:

  • data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
  • dlthub-runtime — Deploy, schedule, and monitor your pipeline in production.
dlt ai toolkit data-exploration install dlt ai toolkit dlthub-runtime install

Was this page helpful?

Community Hub

Need more dlt context for Rappi?

Request dlt skills, commands, AGENT.md files, and AI-native context.