Load Flask-SocketIO data in Python using dltHub

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

In this guide, we'll set up a complete Flask-SocketIO 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 flask_socketio_migration_source(access_token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "http://127.0.0.1/",
            "auth": {
                "type": "bearer",
                "token": access_token,
            },
        },
        "resources": [
            socketio.on('my event'),flask_socketio.send(*message*, **kwargs),flask_socketio.disconnect(*sid=None*, *namespace=None*, *silent=False*)
            ],
    }
    [...]
    yield from rest_api_resources(config)


def get_data() -> None:
    # Connect to destination
    pipeline = dlt.pipeline(
        pipeline_name='flask_socketio_migration_pipeline',
        destination='duckdb',
        dataset_name='flask_socketio_migration_data', 
    )
    # Load the data
    load_info = pipeline.run(flask_socketio_migration_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 flask_socketio_migration’s API and loads it into Iceberg, DataFrames, files, or a database of your choice. Here are some of the endpoints you can load:

Real-Time Communication: Endpoints for managing real-time WebSocket connections and events.
Room Management: Endpoints for handling rooms where users can join or leave.
Message Sending: Endpoints for sending messages to clients in a room or across the application.

You will then debug the Flask-SocketIO 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:

We suggest using a model like Claude 3.7 Sonnet or better
Index the REST API Source tutorial: https://dlthub.com/docs/dlt-ecosystem/verified-sources/rest_api/ and add it to context as @dlt rest api
Read our full steps on setting up Cursor

Now you're ready to get started!

⚙️ Set up dlt Workspace

Install dlt with duckdb support:
```
pip install dlt[workspace]
```
Initialize a dlt pipeline with Flask-SocketIO support.
```
dlt init dlthub:flask_socketio_migration duckdb
```
The init command will setup the necessary files and folders for the next step.

🤠 Start LLM-assisted coding

Here’s a prompt to get you started:

Prompt
Please generate a REST API Source for Flask-SocketIO API, as specified in @flask_socketio_migration-docs.yaml 
Start with endpoints socketio.on('my event') and flask_socketio.send(*message* and skip incremental loading for now. 
Place the code in flask_socketio_migration_pipeline.py and name the pipeline flask_socketio_migration_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 flask_socketio_migration_pipeline.py and await further instructions.

🔒 Set up credentials

The authentication process must be performed before establishing the SocketIO connection, and recent revisions of the Socket.IO protocol allow passing authentication information during the connection.

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

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


python flask_socketio_migration_pipeline.py

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


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

📈 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 flask_socketio_migration_pipeline show --dashboard
```
🐍 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("flask_socketio_migration_pipeline").dataset()
# get ocketio.on('my event' table as Pandas frame
data.ocketio.on('my event'.df().head()
```

Running into errors?

The Flask development server is meant only for development use and should not be used in production. Additionally, a message queue service must be configured when using multiple processes. The application must serve a page to the client that loads the Socket.IO library, and it enforces a same-origin policy by default for security reasons.

Extra resources:

Learn more with our 1h LLM-assisted coding course!