Load Burst-sms data to DuckDB

Burst-sms (Kudosity) is a REST API that enables sending, receiving and managing SMS messages. Everything needed to build a working Burst-sms → 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 Burst-sms to DuckDB pipeline

Paste this prompt into Claude, Codex, or Cursor. The agent does the rest.

PromptCopy prompt
Run uvx dlthub-init@latest to build a pipeline from Burst-sms 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 Burst-sms 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.

---

Burst-sms API at a glance

These values come from the Burst-sms API reference — the authoritative source if anything here looks out of date.

---

How do I authenticate with the Burst-sms API?

Requests use HTTP Basic authentication. The Authorization header must contain the string 'Basic ' followed by the Base64-encoded string of 'API_KEY:API_Secret'.

1. Get your credentials

1. Log in to your Burst SMS (Kudosity) account at the official website.
2. Navigate to the Settings area, typically found in the top menu or dashboard navigation.
3. Locate the API Settings section. 4. If an API Secret is not already set, enter a value (numbers or letters) and save/update your profile.
4. Copy the displayed API Key and API Secret to a secure location for use in your configuration.

2. Add them to .dlt/secrets.toml

Copy
[sources.burst_sms_source]
api_key = "your_api_key_here"
api_secret = "your_api_secret_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 Burst-sms data can I load into DuckDB?

These are the Burst-sms endpoints dlt can load into DuckDB:

---

How do I load only new Burst-sms records?

Burst-sms exposes offset on get-lists.json, so dlt can request only the records that changed since the last run. Set it as the cursor_path and dlt tracks the high-water mark for you between runs.

Copy
{"name": "get_lists", "endpoint": {
    "path": "get-lists.json",
    "data_selector": "lists",
    "incremental": {"cursor_path": "offset", "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 Burst-sms pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading send-sms.json and get-sms-responses.json from the Burst-sms API into DuckDB:

Copy
import dlt
from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources

@dlt.source
def burst_sms_source(api_key=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.transmitsms.com",
            "auth": {"type": "http_basic", "username": "REPLACE_ME", "password": api_key},
        },
        "resources": [
            {"name": "get_lists", "endpoint": {"path": "get-lists.json", "data_selector": "lists"}},
            {"name": "get_list_recipients", "endpoint": {"path": "get-list-recipients.json", "data_selector": "recipients"}}
        ],
    }
    yield from rest_api_resources(config)


def load_burst_sms_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="burst_sms_pipeline",
        destination="duckdb",
        dataset_name="burst_sms_data",
    )
    load_info = pipeline.run(burst_sms_source())
    print(load_info)


if __name__ == "__main__":
    load_burst_sms_to_duckdb()

Run it with python burst_sms_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 Burst-sms 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):

Copy
import dlt

data = dlt.pipeline("burst_sms_pipeline").dataset()
df = data.get_balance.df()
print(df.head())

SQL:

Copy
SELECT * FROM burst_sms_data.get_balance LIMIT 10;

See querying your data with dataset and exploring it in marimo notebooks.

---

How do I deploy the Burst-sms 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 Burst-sms loads into governed, documented models.
• Visualize & share — explore data in notebooks and publish live dashboards instead of static screenshots.

Book a demo →

---

What other destinations can I load Burst-sms data to?

dlt loads into any of these — only the destination argument changes:

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

• Ready for production? Book a demo of the dltHub platform →
• dlt LLM-native workflow docs
• REST API source reference
• Join the dlt community on Slack