MultiPost Python API Docs | dltHub
Build a MultiPost-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
MultiPost API allows remote access to publish content across multiple platforms. It includes RESTful and Browse APIs for task management and content retrieval. The API supports social media data, analytics, and web content crawling. The REST API base URL is https://api.multipost.app/v1 and all requests require a Bearer token in the 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 MultiPost data in under 10 minutes.
What data can I load from MultiPost?
Here are some of the endpoints you can load from MultiPost:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| profile | v1/social/rednote/profile | GET | Retrieve the authenticated user's profile or a profile by user_id query parameter | |
| note | v1/social/rednote/note | GET | Retrieve notes; supports note_id and share_text query parameters | |
| search | v1/social/x/search | GET | General search endpoint supporting keyword, search_type and cursor | |
| followers | v1/social/x/followers | GET | Retrieve followers for authenticated user or by screen_name with pagination via cursor | |
| followings | v1/social/x/followings | GET | Retrieve users followed by authenticated user or by screen_name with pagination | |
| trending | v1/social/x/trending | GET | Retrieve trending topics (optionally by country) | |
| tweet | v1/social/x/tweet | GET | Retrieve a tweet by tweet_id | |
| tweets | v1/social/x/tweets | GET | Retrieve a list of tweets for a user (supports rest_id, screen_name, cursor) | |
| comments | v1/social/x/tweet/comments | GET | Retrieve comments for a tweet (supports tweet_id, cursor) | |
| replies | v1/social/x/replies | GET | Retrieve replies to tweets (supports screen_name, cursor) |
How do I authenticate with the MultiPost API?
MultiPost uses a Bearer token sent in the Authorization header: Authorization: Bearer .
1. Get your credentials
- Sign in to your MultiPost account at https://multipost.app. 2) Open the developer or API section (API / Tokens). 3) Create a new API token and copy the token value. 4) Use the token as a Bearer token in the Authorization header for API calls.
2. Add them to .dlt/secrets.toml
[sources.multipost_source] access_token = "your_multipost_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 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 MultiPost 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 multipost_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline multipost_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset multipost_data The duckdb destination used duckdb:/multipost.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline multipost_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 profile and note from the MultiPost 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 multipost_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.multipost.app/v1", "auth": { "type": "bearer", "token": access_token, }, }, "resources": [ {"name": "profile", "endpoint": {"path": "v1/social/rednote/profile"}}, {"name": "note", "endpoint": {"path": "v1/social/rednote/note"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="multipost_pipeline", destination="duckdb", dataset_name="multipost_data", ) load_info = pipeline.run(multipost_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("multipost_pipeline").dataset() sessions_df = data.profile.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM multipost_data.profile LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("multipost_pipeline").dataset() data.profile.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 MultiPost 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.
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 MultiPost?
Request dlt skills, commands, AGENT.md files, and AI-native context.