Me Integration Python API Docs | dltHub
Build a Me Integration-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Me Integration is a REST API platform for managing Mercado Eletrônico product, order, invoice, supplier and webhook data. The REST API base URL is https://api.mercadoe.com/v1 and All requests require a Bearer token obtained via OAuth2 client credentials..
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 Me Integration data in under 10 minutes.
What data can I load from Me Integration?
Here are some of the endpoints you can load from Me Integration:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| orders | /orders | GET | orders | Retrieve a list of orders with optional query parameters. |
| order_by_id | /orders/{orderId} | GET | Retrieve a single order by its ID. | |
| events | /buckets/{bucketId}/events | GET | events | List webhook events for a specific bucket. |
| products | /products | POST | Create a new product in the catalog. | |
| ack_events | /buckets/{bucketId}/events/ack | POST | Acknowledge receipt of webhook events. |
How do I authenticate with the Me Integration API?
Obtain an access_token via the OAuth2 client‑secret grant and include it in each request as Authorization: Bearer <token>.
1. Get your credentials
- Log in to the ME developer portal.
- Navigate to Credentials.
- Click Create new client.
- Record the generated client_id and client_secret; these are used to request an access_token.
- Store the values securely for use in the dlt pipeline.
2. Add them to .dlt/secrets.toml
[sources.me_integration_source] 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 Me Integration 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 me_integration_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline me_integration_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset me_integration_data The duckdb destination used duckdb:/me_integration.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline me_integration_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 events from the Me Integration 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 me_integration_source(client_secret=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.mercadoe.com/v1", "auth": { "type": "bearer", "token": client_secret, }, }, "resources": [ {"name": "orders", "endpoint": {"path": "orders", "data_selector": "orders"}}, {"name": "events", "endpoint": {"path": "buckets/{bucketId}/events", "data_selector": "events"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="me_integration_pipeline", destination="duckdb", dataset_name="me_integration_data", ) load_info = pipeline.run(me_integration_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("me_integration_pipeline").dataset() sessions_df = data.orders.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM me_integration_data.orders LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("me_integration_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 Me Integration data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example 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.
Troubleshooting
Authentication failures
If the Authorization: Bearer header is missing or contains an invalid token, the API returns a 401 Unauthorized response.
Rate limiting / polling restrictions
"Warning: Do not poll with an interval shorter than 30 seconds to avoid server overload and possible rate limit restrictions." – polling faster than 30 s may trigger HTTP 429 responses.
Pagination quirks
(Documentation did not provide explicit pagination details; implementations should follow standard page and pageSize query parameters when available.)
Ensure that the API key is valid to avoid 401 Unauthorized errors. Also, verify endpoint paths and parameters to avoid 404 Not Found errors.
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 Me Integration?
Request dlt skills, commands, AGENT.md files, and AI-native context.