Load Decodo Instagram Web Scraping API data to DuckDB
Build a Decodo Instagram Web Scraping API to DuckDB pipeline with your coding agent. One prompt scaffolds it with the dltHub AI harness, plus the Decodo Instagram Web Scraping API API base URL, auth, endpoints, and incremental loading.
Decodo is a web-scraping platform that provides managed scraping endpoints, including Instagram and social media scraping, delivering structured JSON outputs for AI and data pipelines. Everything needed to build a working Decodo Instagram Web Scraping API → DuckDB pipeline is on this page: the API's base URL, authentication, endpoints, pagination and incremental field — plus a prompt that hands the whole job to your coding agent.
Build your Decodo Instagram Web Scraping API to DuckDB pipeline
Paste this prompt into Claude, Codex, or Cursor. The agent does the rest.
PromptRunuvx dlthub-init@latestto build a pipeline from Decodo Instagram Web Scraping API to DuckDB and run it on dltHub
That scaffolds a dltHub workspace and installs the dltHub AI harness — the project rules, the secrets-management skill, and the dlt MCP server your agent needs to work safely. From there it reads the Decodo Instagram Web Scraping API API, proposes the endpoints to load, then writes, runs and validates the pipeline while you review rather than type. Credentials are inspected through MCP tools, so your agent never reads secrets.toml itself. How the LLM-native workflow works →
Prefer to write it yourself? Every fact the agent uses is below.
Decodo Instagram Web Scraping API API at a glance
| Base URL | https://scraper-api.decodo.com/v2 |
| Example endpoint | POST v2/scrape |
| Authentication | all requests require a Basic Authentication header using an API token or username/password credentials — sent in the Authorization header, prefixed Basic |
| Pagination | Not paginated |
These values come from the Decodo Instagram Web Scraping API API documentation. Check them against the vendor's current reference before relying on them in production.
How do I authenticate with the Decodo Instagram Web Scraping API API?
All requests require a Basic Authentication header, which consists of the string 'Basic' followed by a space and the base64-encoded user credentials (username:password or token). Required headers include 'Authorization', 'Accept: application/json', and 'Content-Type: application/json'.
1. Get your credentials
To obtain your credentials for the Decodo Web Scraping API, log in to your Decodo dashboard at https://dashboard.decodo.com. Click on your profile icon in the top-right corner, select 'Settings', and navigate to the 'API Keys' tab. From there, you can name and generate your API key or retrieve your username and password for Basic authentication. Note that once you close the generation window, you will not be able to view the full key again, so ensure you save it immediately.
2. Add them to .dlt/secrets.toml
[sources.decodo_instagram_web_scraping_api_source] api_key = "your_api_key_or_basic_auth_token_here"
dlt reads this file automatically at runtime. With the harness, the setup-secrets skill prompts you for the values and never handles the raw credential in chat. For production, see setting up credentials with dlt.
What Decodo Instagram Web Scraping API data can I load into DuckDB?
These are the Decodo Instagram Web Scraping API endpoints dlt can load into DuckDB:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| scrape | /v2/scrape | POST | Real-time (synchronous) scraping request | |
| task_create | /v3/task | POST | Initiate asynchronous scraping task | |
| task_results | /v3/task/{task_id}/results | GET | Retrieve results for an async scraping task | |
| task_batch | /v3/task/batch | POST | Initiate batch asynchronous scraping | |
| endpoints | /v1/endpoints | GET | Retrieve available proxy endpoints |
How do I load only new Decodo Instagram Web Scraping API records?
The Decodo Instagram Web Scraping API API reference does not document a timestamp or sequence field for these endpoints, so there is nothing to advertise here as verified. Pick a field from the endpoints table above that increases with every write, then set it as the cursor_path.
{"name": "scrape", "endpoint": { "path": "v2/scrape", # Replace with a field that increases on every write. "incremental": {"cursor_path": "REPLACE_ME", "initial_value": "2024-01-01T00:00:00Z"}, }}
On the first run dlt loads everything from initial_value; on every run after that it requests only what changed and appends with write_disposition="merge" if you set a primary key. See incremental loading.
What does the generated Decodo Instagram Web Scraping API pipeline look like?
A standard dlt REST API pipeline — the same code you would write by hand, loading /v2/scrape and /v3/task from the Decodo Instagram Web Scraping API API into DuckDB:
import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def decodo_instagram_web_scraping_api_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://scraper-api.decodo.com/v2", "auth": {"type": "http_basic", "username": "REPLACE_ME", "password": api_key}, }, "resources": [ {"name": "scrape", "endpoint": {"path": "v2/scrape"}}, {"name": "task_results", "endpoint": {"path": "v3/task/{task_id}/results"}} ], } yield from rest_api_resources(config) def load_decodo_instagram_web_scraping_api_to_duckdb() -> None: pipeline = dlt.pipeline( pipeline_name="decodo_instagram_web_scraping_api_pipeline", destination="duckdb", dataset_name="decodo_instagram_web_scraping_api_data", ) load_info = pipeline.run(decodo_instagram_web_scraping_api_source()) print(load_info) if __name__ == "__main__": load_decodo_instagram_web_scraping_api_to_duckdb()
Run it with python decodo_instagram_web_scraping_api_pipeline.py. The agent iterates on this until it loads cleanly — you review and approve, rather than write it from scratch.
How do I query Decodo Instagram Web Scraping API data in DuckDB?
dlt creates one table per resource. Query the loaded data with Python or SQL — or ask your agent to, through the MCP server's execute_sql_query tool.
Python (pandas DataFrame):
import dlt data = dlt.pipeline("decodo_instagram_web_scraping_api_pipeline").dataset() df = data.scrape.df() print(df.head())
SQL:
SELECT * FROM decodo_instagram_web_scraping_api_data.scrape LIMIT 10;
See querying your data with dataset and exploring it in marimo notebooks.
How do I deploy the Decodo Instagram Web Scraping API to DuckDB pipeline in production?
The pipeline runs locally, which is ideal for prototyping and one-off analysis. When you need it on a schedule, monitored on every load, and shared with your team, deploy the same dlt code on the dltHub platform — no infrastructure to maintain. The prompt above already ends with "run it on dltHub", so your agent can take it there directly.
- Deploy & schedule — run the pipeline as a managed job with automatic retries.
- Monitor — observable job queues, alerting, and load metrics for every run.
- Transform — promote raw Decodo Instagram Web Scraping API loads into governed, documented models.
- Visualize & share — explore data in notebooks and publish live dashboards instead of static screenshots.
What other destinations can I load Decodo Instagram Web Scraping API data to?
dlt loads into any of these — only the destination argument changes:
| Destination | Example value |
|---|---|
| PostgreSQL | "postgres" |
| BigQuery | "bigquery" |
| Snowflake | "snowflake" |
| Redshift | "redshift" |
| Databricks | "databricks" |
| Filesystem (S3, GCS, Azure) | "filesystem" |
Set dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. On the dltHub platform the same pipeline runs against a managed Iceberg lakehouse. See the full destinations list.
Next steps
Was this page helpful?
Community Hub
Need more dlt context for Decodo Instagram Web Scraping API to DuckDB?
Request dlt skills, commands, AGENT.md files, and AI-native context.