Load Ace Stream data in Python using dltHub

Build a Ace Stream-to-database or-dataframe pipeline in Python using dlt with automatic Cursor support.

In this guide, we'll set up a complete Ace Stream data pipeline from API credentials to your first data load in just 10 minutes. You'll end up with a fully declarative Python pipeline based on dlt's REST API connector, like in the partial example code below:

Example code
@dlt.source
def ace_stream_migrations_source(access_token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "http://127.0.0.1:6878/",
            "auth": {
                "type": "bearer",
                "token": access_token,
            },
        },
        "resources": [
            bind,,play,,burn
            ],
    }
    [...]
    yield from rest_api_resources(config)


def get_data() -> None:
    # Connect to destination
    pipeline = dlt.pipeline(
        pipeline_name='ace_stream_migrations_pipeline',
        destination='duckdb',
        dataset_name='ace_stream_migrations_data', 
    )
    # Load the data
    load_info = pipeline.run(ace_stream_migrations_source())
    print(load_info)

Why use dltHub Workspace with LLM Context to generate Python pipelines?

  • Accelerate pipeline development with AI-native context
  • Debug pipelines, validate schemas and data with the integrated Pipeline Dashboard
  • Build Python notebooks for end users of your data
  • Low maintenance thanks to Schema evolution with type inference, resilience and self documenting REST API connectors. A shallow learning curve makes the pipeline easy to extend by any team member
  • dlt is the tool of choice for Pythonic Iceberg Lakehouses, bringing mature data loading to pythonic Iceberg with or without catalogs

What you’ll do

We’ll show you how to generate a readable and easily maintainable Python script that fetches data from ace_stream_migrations’s API and loads it into Iceberg, DataFrames, files, or a database of your choice. Here are some of the endpoints you can load:

  • Bind: Creates a new binding.
  • Play: Starts playback of content.
  • Burn: Removes specific content.
  • Mint: Issues new tokens or content.
  • Pools: Manages liquidity pools.
  • Search: Searches for available content.
  • Pricing: Retrieves pricing information.
  • Oracles: Interacts with oracle services.
  • Issuing: Manages token issuance.
  • Geotags: Handles geographic tagging.
  • Convert: Converts one token to another.
  • Ace Time: Provides time-related services.
  • Load Async: Loads data asynchronously.
  • Ace Byte: Manages byte-level operations.
  • Server API: Interacts with server-level functions.
  • Get Status: Checks the current status of the service.
  • Add Device: Registers a new device.
  • Operations: Handles various operations related to the service.
  • Service API: Provides additional service-related functions.
  • Playlist Get: Retrieves a playlist.

You will then debug the Ace Stream pipeline using our Pipeline Dashboard tool to ensure it is copying the data correctly, before building a Notebook to explore your data and build reports.

Setup & steps to follow

💡
Before getting started, let's make sure Cursor is set up correctly:

Now you're ready to get started!

  1. ⚙️ Set up dlt Workspace

    Install dlt with duckdb support:

    pip install "dlt[workspace]"

    Initialize a dlt pipeline with Ace Stream support.

    dlt init dlthub:ace_stream_migrations duckdb

    The init command will setup the necessary files and folders for the next step.

  2. 🤠 Start LLM-assisted coding

    Here’s a prompt to get you started:

    Prompt
    Please generate a REST API Source for Ace Stream API, as specified in @ace_stream_migrations-docs.yaml 
Start with endpoints bind and  and skip incremental loading for now. 
Place the code in ace_stream_migrations_pipeline.py and name the pipeline ace_stream_migrations_pipeline. 
If the file exists, use it as a starting point. 
Do not add or modify any other files. 
Use @dlt rest api as a tutorial. 
After adding the endpoints, allow the user to run the pipeline with python ace_stream_migrations_pipeline.py and await further instructions.

  3. 🔒 Set up credentials

    Public methods can be accessed without an access token, while private methods require an access token in the request parameters. Ensure that the access token is valid and not expired.

    To get the appropriate API keys, please visit the original source at https://www.acestream.org/. If you want to protect your environment secrets in a production environment, look into setting up credentials with dlt.

  4. 🏃‍♀️ Run the pipeline in the Python terminal in Cursor

    python ace_stream_migrations_pipeline.py

    If your pipeline runs correctly, you’ll see something like the following:

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

  5. 📈 Debug your pipeline and data with the Pipeline Dashboard

    Now that you have a running pipeline, you need to make sure it’s correct, so you do not introduce silent failures like misconfigured pagination or incremental loading errors. By launching the dlt Workspace Pipeline Dashboard, you can see various information about the pipeline to enable you to test it. Here you can see:

    • Pipeline overview: State, load metrics
    • Data’s schema: tables, columns, types, hints
    • You can query the data itself
    dlt pipeline ace_stream_migrations_pipeline show

  6. 🐍 Build a Notebook with data explorations and reports

    With the pipeline and data partially validated, you can continue with custom data explorations and reports. To get started, paste the snippet below into a new marimo Notebook and ask your LLM to go from there. Jupyter Notebooks and regular Python scripts are supported as well.

    import dlt

data = dlt.pipeline("ace_stream_migrations_pipeline").dataset()
# get in table as Pandas frame
data.in.df().head()

Running into errors?

Private methods require an access token, and the token must be retrieved from a trusted environment. Be mindful of the network's limitations, including potential congestion and inefficiency. Operations are limited to one transaction every 24 hours and may be affected by external factors. Ensure that you are compliant with the DMCA terms while using the service.

Extra resources:

Next steps