Slybroadcast Python API Docs | dltHub

Slybroadcast is a voicemail broadcasting service that lets you send pre‑recorded audio messages to phone numbers via an API. The REST API base URL is https://www.mobile-sphere.com/gateway and All requests require the account email (c_uid) and password (c_password) sent as form fields..

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 Slybroadcast data in under 10 minutes.

---

What data can I load from Slybroadcast?

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

---

How do I authenticate with the Slybroadcast API?

Authentication is performed by including the account email (c_uid) and password (c_password) as form fields in each POST request. No additional headers are required.

1. Get your credentials

1. Log in to your Slybroadcast account at https://www.slybroadcast.com.
2. Navigate to the "Account Settings" or "Profile" section.
3. Locate the API credentials area; the login email (c_uid) is shown, and the password (c_password) is the same password you use to log in.
4. If you have forgotten the password, use the "Forgot Password" link to reset it, then use the new password as c_password.
5. Record the email and password; they will be used in the dlt source configuration.

2. Add them to .dlt/secrets.toml

Copy
[sources.slybroadcast_source]
c_uid = "your_email@example.com"
c_password = "your_password"

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:

Copy
uv venv && source .venv/bin/activate
uv pip install "dlt[workspace]"

1. Install the dlt AI Workbench:

Copy
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:

Copy
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 Slybroadcast 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:

Copy
python slybroadcast_pipeline.py

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

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

Inspect your pipeline and data:

Copy
dlt pipeline slybroadcast_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 audio_list and campaign_results from the Slybroadcast API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

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

@dlt.source
def slybroadcast_source(c_uid=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://www.mobile-sphere.com/gateway",
            "auth": {
                "type": "api_key",
                "api_key": c_uid,
            },
        },
        "resources": [
            {"name": "audio_list", "endpoint": {"path": "gateway/vmb.aflist.php"}},
            {"name": "campaign_results", "endpoint": {"path": "gateway/vmb.json.php"}}
        ],
    }
    yield from rest_api_resources(config)


def get_data() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="slybroadcast_pipeline",
        destination="duckdb",
        dataset_name="slybroadcast_data",
    )
    load_info = pipeline.run(slybroadcast_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):

Copy
import dlt

data = dlt.pipeline("slybroadcast_pipeline").dataset()
sessions_df = data.audio_list.df()
print(sessions_df.head())

SQL (DuckDB example):

Copy
SELECT * FROM slybroadcast_data.audio_list LIMIT 10;

In a marimo or Jupyter notebook:

Copy
import dlt

data = dlt.pipeline("slybroadcast_pipeline").dataset()
data.audio_list.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 Slybroadcast data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.

---

Troubleshooting

Authentication Errors

• If c_uid or c_password are missing or invalid, the API returns a JSON object like {"ERROR":"c_uid: required; c_password: required; c_option or c_method required; "}. Ensure both fields are included in every request.

Invalid Method or Missing Parameters

• Omitting c_method or providing an unsupported value results in the same ERROR structure. Verify the c_method value matches one of the documented actions.

Rate Limits & Pagination

• The API documentation does not specify rate‑limit headers or pagination parameters. Empirically, the service limits a single campaign to 10,000 phone numbers. Implement client‑side throttling if you encounter HTTP 429 responses.

General HTTP Errors

• Non‑JSON endpoints may return plain‑text error lines such as ERROR 9145797854 <session_id> invalid or not found. Treat any non‑200 HTTP status as a failure and log the response body for debugging.

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.

Copy
dlt ai toolkit data-exploration install
dlt ai toolkit dlthub-runtime install

• How to deploy a pipeline
• How to explore your data in marimo Notebooks
• How to query your data in Python with dataset
• Join the dlt community on Slack