Load Soundcloud data to Google Cloud Storage

SoundCloud is an audio platform API for accessing public and authorized user music resources. Everything needed to build a working Soundcloud → Google Cloud Storage 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 Soundcloud to Google Cloud Storage pipeline

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

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 Soundcloud 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.

---

Soundcloud API at a glance

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

---

How do I authenticate with the Soundcloud API?

Send the access token on every API request as the HTTP header Authorization: OAuth <access_token>. SoundCloud documents the token endpoint at https://secure.soundcloud.com/oauth/token; token acquisition uses OAuth 2.1, with PKCE required for the authorization-code flow. The API guide also shows Accept: application/json; charset=utf-8 and form-urlencoded content type for token exchange, but does not establish that these are required on ordinary GET requests.

1. Get your credentials

1. Obtain a SoundCloud Artist Pro subscription; SoundCloud currently requires Artist Pro to register API applications and receive public-API credentials. 2. Recommended CLI method: ensure Node.js 18+ is installed, then run the SoundCloud API credential script with your app metadata, for example: curl -fsSL https://raw.githubusercontent.com/soundcloud/api/master/scripts/sc-api-auth.mjs | node --input-type=module - --remote --name "My API App" --description "What my integration does" --website "https://example.com". 3. Open the printed https://secure.soundcloud.com/activate/... pairing URL, sign in to SoundCloud, and approve the pairing. 4. The CLI creates or retrieves the app and prints its Client ID and Client Secret; store the secret in an environment variable or secrets manager and never commit or expose it. 5. Browser alternative: open SoundCloud Your Apps, create an application, enter its name, description, and website, accept the terms, then copy the Client ID and Client Secret. 6. For public resources, exchange those credentials at https://secure.soundcloud.com/oauth/token using OAuth client credentials: send grant_type=client_credentials as form data and HTTP Basic authentication containing base64(client_id
   ). The resulting bearer-style access token is sent to API requests in Authorization: OAuth ACCESS_TOKEN (SoundCloud's documented header prefix is OAuth, not Bearer).

2. Add them to .dlt/secrets.toml

Copy
[sources.soundcloud_source]
client_id = "your_soundcloud_client_id"
client_secret = "your_soundcloud_client_secret"

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 Soundcloud data can I load into Google Cloud Storage?

These are the Soundcloud endpoints dlt can load into Google Cloud Storage:

---

How do I load only new Soundcloud records?

Soundcloud exposes created_at on users/{user_urn}/tracks, 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": "user_tracks", "endpoint": {
    "path": "users/{user_urn}/tracks",
    "data_selector": "collection",
    "incremental": {"cursor_path": "created_at", "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 Soundcloud pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading tracks and users/

/tracks from the Soundcloud API into Google Cloud Storage:

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

@dlt.source
def soundcloud_source(access_token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.soundcloud.com",
            "auth": {"type": "bearer", "token": access_token},
        },
        "resources": [
            {"name": "user_tracks", "endpoint": {"path": "users/{user_urn}/tracks", "data_selector": "collection"}},
            {"name": "tracks", "endpoint": {"path": "tracks", "data_selector": "collection"}}
        ],
    }
    yield from rest_api_resources(config)


def load_soundcloud_to_google_cloud_storage_filesystem() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="soundcloud_pipeline",
        destination="filesystem",
        dataset_name="soundcloud_data",
    )
    load_info = pipeline.run(soundcloud_source())
    print(load_info)


if __name__ == "__main__":
    load_soundcloud_to_google_cloud_storage_filesystem()

Run it with uv run python soundcloud_pipeline.py. The agent iterates on this until it loads cleanly — you review and approve, rather than write it from scratch.

---

How do I configure Google Cloud Storage as the destination?

dlt writes to Google Cloud Storage through its filesystem destination; the gs:// scheme in bucket_url selects it. Install the extra with uv add "dlt[gs]", then add to .dlt/config.toml and .dlt/secrets.toml:

Copy
# .dlt/config.toml
[destination.filesystem]
bucket_url = "gs://<bucket>/<path>"

# .dlt/secrets.toml
[destination.filesystem.credentials]
project_id = "<project id>"
private_key = "<private key>"
client_email = "<service account email>"

dlt writes JSONL by default; pass loader_file_format="parquet" to pipeline.run() for Parquet. Delta and Iceberg table formats are supported too. See the dlt filesystem destination docs.

Changing bucket_url is all it takes to write the same data to Amazon S3, Azure Blob Storage or local files instead; see dlt's filesystem destination for all four.

---

How do I query Soundcloud data in Google Cloud Storage?

After a run, pipeline.dataset() holds the loaded tables, one per resource. A Relation is a query on that dataset, either a whole table or a SQL string, and reading it gives you the data as a Pandas DataFrame, a PyArrow table or Python tuples. Nothing is read until you ask for it. A filesystem destination holds files rather than tables, so dlt reads them through DuckDB views and the interface is the same as for a SQL destination; for frequent reads load Delta or Iceberg tables, which DuckDB reads only as far as the query needs (see reading data from filesystem).

Copy
import dlt

pipeline = dlt.pipeline("soundcloud_pipeline")

# Step 1: Get the dataset from the pipeline
dataset = pipeline.dataset()

# Step 2: Get a Relation, either a whole table...
tracks = dataset.table("tracks")
# ...or any SQL query against Google Cloud Storage
sample = dataset("SELECT * FROM tracks LIMIT 100")

# Step 3: Read the data
df = tracks.df()  # or .df(chunk_size=50) for a large table
arrow_table = sample.arrow()  # a PyArrow Table
rows = sample.fetchall()  # a list of Python tuples

# Which tables were loaded, and how big are they?
print(dataset.row_counts().df())
"""
    table_name  row_count
0  user_tracks         13
1       tracks          3
"""

The columns are the fields the Soundcloud API returns. Your agent can run the same queries through the MCP server's execute_sql_query tool, and uv run dlthub show opens the Pipeline Dashboard with the schema, load metrics and a query box. See access loaded data in Python and exploring it in marimo notebooks.

---

How do I deploy the Soundcloud to Google Cloud Storage 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 Soundcloud 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 Soundcloud 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