Facebook-messenger Python API Docs | dltHub
Build a Facebook-messenger-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Facebook Messenger Platform is a set of APIs that enable sending and receiving messages, managing conversations, and configuring page messenger settings. The REST API base URL is https://graph.facebook.com and All requests require a Page Access Token passed as the access_token query parameter..
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 Facebook-messenger data in under 10 minutes.
What data can I load from Facebook-messenger?
Here are some of the endpoints you can load from Facebook-messenger:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| accounts | /me/accounts | GET | data | Retrieves pages the user manages and their access tokens |
| conversations | /{page-id}/conversations | GET | data | Lists conversation IDs for a page |
| messages | /{conversation-id} | GET | messages.data | Retrieves messages within a conversation |
| messenger_profile | /{page-id}/messenger_profile | GET | data | Gets the page's messenger profile settings |
| insights | /{page-id}/insights | GET | data | Retrieves analytics insights for the page |
How do I authenticate with the Facebook-messenger API?
Authentication is performed using a Page Access Token supplied as the access_token query parameter on every request.
1. Get your credentials
- Log in to the Facebook Developer portal (https://developers.facebook.com).
- Select your app or create a new one.
- In the left menu, go to Products → Facebook Login → Settings and ensure the
pages_messagingpermission is approved. - Navigate to Tools → Graph API Explorer.
- Choose your app, select the Page you manage, and click Generate Access Token with the
pages_messagingpermission. - Copy the generated token; it is the Page Access Token required for the Messenger API.
- (Optional) Extend the short‑lived token to a long‑lived token via the Access Token Debugger.
2. Add them to .dlt/secrets.toml
[sources.facebook_messenger_source] access_token = "your_page_access_token"
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 Facebook-messenger 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 facebook_messenger_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline facebook_messenger_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset facebook_messenger_data The duckdb destination used duckdb:/facebook_messenger.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline facebook_messenger_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 conversations and messages from the Facebook-messenger 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 facebook_messenger_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://graph.facebook.com", "auth": { "type": "api_key", "api_key": access_token, }, }, "resources": [ {"name": "conversations", "endpoint": {"path": "{page-id}/conversations", "data_selector": "data"}}, {"name": "messages", "endpoint": {"path": "{conversation-id}", "data_selector": "messages.data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="facebook_messenger_pipeline", destination="duckdb", dataset_name="facebook_messenger_data", ) load_info = pipeline.run(facebook_messenger_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("facebook_messenger_pipeline").dataset() sessions_df = data.conversations.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM facebook_messenger_data.conversations LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("facebook_messenger_pipeline").dataset() data.conversations.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 Facebook-messenger 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 Errors
- Error 190: Invalid OAuth access token – ensure the Page Access Token is correct and not expired.
- Error 200: Permissions error – the token must have the
pages_messagingpermission.
Rate Limits
- The Messenger Platform enforces a limit of 20 messages per second per Page. Exceeding this returns error code 613 (Rate limit exceeded). Implement exponential backoff.
Pagination
- List endpoints (e.g., conversations, messages) use cursor‑based pagination. Include the
aftercursor from the responsepaging.nextURL to retrieve the next page of results.
General API Errors
- Error 100: Parameter validation error – verify required query parameters like
access_tokenare present. - Error 4: Application request limit reached – spread requests over time or request higher limits via Facebook.
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 Facebook-messenger?
Request dlt skills, commands, AGENT.md files, and AI-native context.