Load Token Transit data in Python using dltHub

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

In this guide, we'll set up a complete Token Transit 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 token_transit_source(access_token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.tokentransit.com/user",
            "auth": {
                "type": "bearer",
                "token": access_token,
            }
        },
        "resources": [
            "login", "stripe_ephemeral_key`"
        ],
    }
    [...]
    yield from rest_api_resources(config)


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

  • Agency Endpoints: Endpoints related to transportation agencies, including fare information and specific agency details.

    • /agency: General information about transportation agencies.
    • /agency/bigbluebus: Details specific to the Big Blue Bus agency.
    • /agency/bigbluebus/fare: Fare-related information for the Big Blue Bus.
    • /agency/bigbluebus/fare/regular_single_ride/purchase: Purchase endpoint for a regular single ride fare.

  • User Endpoints: Endpoints for user authentication and management.

    • /user/login: Endpoint for user login.
    • /user/logout: Endpoint for user logout.
    • /user/stripe_ephemeral_key: Endpoint to obtain a Stripe ephemeral key for payment processing.

  • Pass Endpoints: Endpoints related to transit passes.

    • /pass: General information or management for passes.
    • /pass/{pass_id}: Retrieve or manage a specific pass by its ID.
    • /pass/pass_unactivated: Endpoint for unactivated passes.
    • /pass/pass_unactivated/activate: Activate an unactivated pass.

  • Purchase Endpoints: Endpoints related to purchasing tickets or fares.

    • /purchase: General purchase endpoint for transactions.
    • /redeem: Endpoint for redeeming tickets or passes.

  • Cart Endpoints: Endpoints related to shopping cart functionality.

    • /cart: Endpoint for managing the user's shopping cart.

  • Validation Endpoints: Endpoints for validating tickets or passes visually.

    • /validation/visual: Endpoint for visual validation of tickets or passes.

  • Miscellaneous Endpoints: Other various endpoints that may not fit into the above categories.

    • /pass?ticket_format=none&omit_unusabled_passes=false&include_fare_price=false: Endpoint with specific query parameters for pass retrieval.

You will then debug the Token Transit 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 Token Transit support.

    dlt init dlthub:token_transit 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 Token Transit API, as specified in @token_transit-docs.yaml 
Start with endpoints login and stripe_ephemeral_key` and skip incremental loading for now. 
Place the code in token_transit_pipeline.py and name the pipeline token_transit_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 token_transit_pipeline.py and await further instructions.

  3. 🔒 Set up credentials

    A secret key is required and can be obtained by following the instructions in the documentation; it should be applied as specified in the relevant API calls.

    To get the appropriate API keys, please visit the original source at https://www.tokentransit.com/developer/docs/api/ticketing.html. 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 token_transit_pipeline.py

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

    Pipeline token_transit load step completed in 0.26 seconds
1 load package(s) were loaded to destination duckdb and into dataset token_transit_data
The duckdb destination used duckdb:/token_transit.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 token_transit_pipeline show dashboard

  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("token_transit_pipeline").dataset()
# get "login" table as Pandas frame
data."login".df().head()

Extra resources:

Next steps