Mogo Python API Docs | dltHub

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

Last updated:

Mogo API is an SMS messaging platform that allows sending SMS messages, retrieving delivery reports, checking account credits, and receiving inbound SMS via webhooks. The REST API base URL is https://api.mogo.io/ (staging: https://api-staging.mogo.io/, sandbox: https://sandbox-api.mogo.io/) and all requests require an API key pair in HTTP 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 pip install "dlt[workspace]" and start loading Mogo data in under 10 minutes.


What data can I load from Mogo?

Here are some of the endpoints you can load from Mogo:

ResourceEndpointMethodData selectorDescription
send_message/sendmessagePOSTSend SMS to one or more recipients
delivery_report/deliveryreportGETRetrieve delivery status for previously sent messages
credit_check/creditcheckGETCheck account credit balance
incoming_messages_webhook(webhook POST endpoint configured by user)POSTReceive inbound SMS via webhook (no list key; payload contains single message or array depending on configuration)
services/services?type=amcGETFetch services available for account (returns JSON list)

How do I authenticate with the Mogo API?

The API requires a matching pair of API Keys supplied in request headers. Contact Mogo to obtain keys. Excessive requests with incorrect auth may result in IP blocking for 30 minutes.

1. Get your credentials

  1. Contact Mogo support or your Mogo account manager requesting API credentials. 2) Mogo will provide an API key pair (key_id and key_value). 3) Use the provided keys in request headers on every API call. 4) For sandbox testing request separate sandbox keys from Mogo.

2. Add them to .dlt/secrets.toml

[sources.mogo_source] key_id = "YOUR_KEY_ID" key_value = "YOUR_KEY_VALUE"

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 Mogo 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 mogo_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline mogo_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 send_message and delivery_report from the Mogo 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 mogo_source(api_key_pair=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.mogo.io/ (staging: https://api-staging.mogo.io/, sandbox: https://sandbox-api.mogo.io/)", "auth": { "type": "api_key", "api_key (config holds keys: key_id and key_value; dlt config should store both)": api_key_pair, }, }, "resources": [ {"name": "send_message", "endpoint": {"path": "sendmessage"}}, {"name": "delivery_report", "endpoint": {"path": "deliveryreport"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="mogo_pipeline", destination="duckdb", dataset_name="mogo_data", ) load_info = pipeline.run(mogo_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("mogo_pipeline").dataset() sessions_df = data.delivery_report.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM mogo_data.delivery_report LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("mogo_pipeline").dataset() data.delivery_report.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 Mogo 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.


Troubleshooting

Authentication failures

If requests return 401 Unauthorized or 402 Payment Required, verify key_id and key_value are correct and included in headers. Too many incorrect auth attempts may cause the client IP to be blocked for 30 minutes.

Rate limits and throttling

If you receive 429 Too Fast, you have exceeded throttling limits; implement exponential backoff and reduce request rate.

Insufficient credits

402 Payment Required indicates insufficient credits; top up account to resume sending messages.

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 Mogo?

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