Load Applivery data in Python using dltHub

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

In this guide, we'll set up a complete Applivery 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 applivery_source(access_token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://dashboard.applivery.io/api/",
            {
    "type": "bearer",
    "token": access_token,
},
        },
        "resources": [
            "apps",
"builds",
"devices"
        ],
    }
    [...]
    yield from rest_api_resources(config)


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

  • Apps Management: Basic API endpoints for managing mobile applications with limited scope
  • Builds Management: Endpoints for handling application builds, deployments, and version control
  • Device Management: Endpoints for managing mobile devices, tablets, desktop and TV devices across Android and iOS platforms
  • Publications: Endpoints for managing app publications and distribution workflows
  • Workspace Management: Advanced API endpoints providing access to all platform functionality including service accounts and user management

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

    dlt init dlthub:applivery 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 Applivery API, as specified in @applivery-docs.yaml 
Start with endpoints "apps" and "builds" and skip incremental loading for now. 
Place the code in applivery_pipeline.py and name the pipeline applivery_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 applivery_pipeline.py and await further instructions.

  3. 🔒 Set up credentials

    Applivery uses API key authentication with two tiers: Apps API provides basic functionality with limited scope, while Workspace API provides advanced access to all endpoints. Service Accounts can generate perpetual role-based authentication tokens for automated integrations.

    To get the appropriate API keys, please visit the original source at https://www.applivery.com/. 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 applivery_pipeline.py

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

    Pipeline applivery load step completed in 0.26 seconds
1 load package(s) were loaded to destination duckdb and into dataset applivery_data
The duckdb destination used duckdb:/applivery.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 applivery_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("applivery_pipeline").dataset()
# get apps table as Pandas frame
data.apps.df().head()

Running into errors?

The platform has two API tiers with different access levels - Apps API has limited scope while Workspace API provides full access. Service Accounts are required for perpetual authentication tokens. The platform processes device geolocation data when MDM tracking is enabled and uses third-party payment processors. Data retention is based on legitimate business needs and legal requirements.

Extra resources:

Next steps

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

- Apps Management: Basic API endpoints for managing mobile applications with limited scope
- Builds Management: Endpoints for handling application builds, deployments, and version control
- Device Management: Endpoints for managing mobile devices, tablets, desktop and TV devices across Android and iOS platforms
- Publications: Endpoints for managing app publications and distribution workflows
- Workspace Management: Advanced API endpoints providing access to all platform functionality including service accounts and user management

You will then debug the Applivery 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

```default
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](https://dlthub.com/docs/dlt-ecosystem/llm-tooling/cursor-restapi#23-configuring-cursor-with-documentation)

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 Applivery support.

    dlt init dlthub:applivery 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 Applivery API, as specified in @applivery-docs.yaml 
Start with endpoints "apps" and "builds" and skip incremental loading for now. 
Place the code in applivery_pipeline.py and name the pipeline applivery_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 applivery_pipeline.py and await further instructions.

  3. 🔒 Set up credentials

    Applivery uses API key authentication with two tiers: Apps API provides basic functionality with limited scope, while Workspace API provides advanced access to all endpoints. Service Accounts can generate perpetual role-based authentication tokens for automated integrations.

    To get the appropriate API keys, please visit the original source at https://www.applivery.com/. 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 applivery_pipeline.py

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

    Pipeline applivery load step completed in 0.26 seconds
1 load package(s) were loaded to destination duckdb and into dataset applivery_data
The duckdb destination used duckdb:/applivery.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 applivery_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("applivery_pipeline").dataset()
# get apps table as Pandas frame
data.apps.df().head()

Running into errors?

The platform has two API tiers with different access levels - Apps API has limited scope while Workspace API provides full access. Service Accounts are required for perpetual authentication tokens. The platform processes device geolocation data when MDM tracking is enabled and uses third-party payment processors. Data retention is based on legitimate business needs and legal requirements.

Extra resources:

Next steps