Load Reviews And Ratings Api data in Python using dltHub

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

Last updated:

VTEX Reviews and Ratings API allows store owners and developers to manage, submit, and retrieve customer product reviews and star ratings for their e-commerce storefronts. The REST API base URL is https://{accountName}.myvtex.com and all requests require X-VTEX-API-AppKey and X-VTEX-API-AppToken headers.

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 add "dlt[hub]" and start loading Reviews And Ratings Api data in under 10 minutes.


What data can I load from Reviews And Ratings Api?

Here are some of the endpoints you can load from Reviews And Ratings Api:

ResourceEndpointMethodData selectorDescription
reviews/reviewsGETreviewsReturns a list of reviews
reviews/reviews/{id}GETReturns a single review by ID
review_stats/reviews/statsGETReturns aggregate review statistics
review_products/reviews/productsGETproductsReturns a list of products with review stats
review_search/reviews/searchPOSTresultsHybrid search over review content

How do I authenticate with the Reviews And Ratings Api API?

Requests are authenticated by providing an application key and application token pair in the HTTP headers: 'X-VTEX-API-AppKey' and 'X-VTEX-API-AppToken'.

1. Get your credentials

To obtain API credentials, log in to your provider's merchant or developer dashboard. Navigate to the Settings or API management section, typically labeled 'API' or 'Developers.' For platforms using OAuth 2.0 (e.g., Emplifi/TurnTo, Trustpilot), you will retrieve a client_id and client_secret to authenticate via a token endpoint. For platforms using API keys (e.g., REVIEWS.ai, ResellerRatings), select the 'Generate' or 'Create' button to produce a secure, unique API token or key. Always store these credentials securely and avoid exposing them in public code repositories.

2. Add them to .dlt/secrets.toml

[sources.reviews_and_ratings_api_source] api_key = "your_private_api_key_here" # OR, if using OAuth2 bearer tokens: bearer_token = "your_bearer_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 init uv add "dlt[hub]"

1. Install the dlt AI harness:

uv run dlthub 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:

uv run dlthub ai toolkit install rest-api-pipeline

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 Reviews And Ratings Api 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:

uv run python reviews_and_ratings_api_pipeline.py

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

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

Inspect your pipeline and data:

uv run dlthub 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 GET /reviews and POST /reviews from the Reviews And Ratings Api 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 reviews_and_ratings_api_source(app_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://{accountName}.myvtex.com", "auth": {"type": "api_key", "api_key": app_key, "name": "app_token"}, }, "resources": [ {"name": "reviews", "endpoint": {"path": "reviews", "data_selector": "reviews"}}, {"name": "reviews_query", "endpoint": {"path": "reviews/query", "data_selector": "results"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="reviews_and_ratings_api_pipeline", destination="duckdb", dataset_name="reviews_and_ratings_api_data", ) load_info = pipeline.run(reviews_and_ratings_api_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("reviews_and_ratings_api_pipeline").dataset() sessions_df = data.reviews.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM reviews_and_ratings_api_data.reviews LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("reviews_and_ratings_api_pipeline").dataset() data.reviews.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 Reviews And Ratings Api 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 harness:

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

Was this page helpful?

Community Hub

Need more dlt context for Reviews And Ratings Api?

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