Load CleverPush data in Python using dltHub
Build a CleverPush-to-database or-dataframe pipeline in Python using dlt with automatic Cursor support.
In this guide, we'll set up a complete CleverPush 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
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 cleverpush’s API and loads it into Iceberg, DataFrames, files, or a database of your choice. Here are some of the endpoints you can load:
- Notification Templates: Endpoints related to managing notification templates for specific channels.
- Notification Events: Endpoints for handling events associated with notifications for specific channels.
- Media Uploads: Endpoint for uploading media files for notifications.
- Follow-Up Campaigns: Endpoints for creating and managing follow-up campaigns linked to specific channels.
- Bulk Notification Sending: Endpoint for sending notifications in bulk.
- Channel Tags: Endpoints for managing tags associated with specific channels.
- Channel Stories: Endpoints for handling stories related to specific channels.
- Projects: Endpoint listing and managing projects.
- App Banners: Endpoints for managing app banners associated with specific channels.
- Subscription Tagging: Endpoints for tagging and untagging subscriptions associated with channels.
- Notification Campaigns: Endpoints for managing notification campaigns linked to specific channels.
- Email Opt-In Routines: Endpoints for managing email opt-in routines for specific channels.
- Web Banners: Endpoints for managing web banners associated with specific channels.
- Geo-Fences: Endpoints for managing geo-fences linked to specific channels.
- Wallet Pass Subscriptions: Endpoints for subscribing to wallet passes associated with specific channels.
- Tag Statistics: Endpoints for retrieving statistics related to specific tags in channels.
- Notification Template Details: Endpoints for retrieving details of specific notification templates associated with channels.
You will then debug the CleverPush 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
dltWorkspaceInstall dlt with duckdb support:
pip install "dlt[workspace]"Initialize a dlt pipeline with CleverPush support.
dlt init dlthub:cleverpush duckdbThe
initcommand will setup the necessary files and folders for the next step. -
🤠 Start LLM-assisted coding
Here’s a prompt to get you started:
PromptPlease generate a REST API Source for CleverPush API, as specified in @cleverpush-docs.yaml Start with endpoints hourly-statistics and statistics and skip incremental loading for now. Place the code in cleverpush_pipeline.py and name the pipeline cleverpush_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 cleverpush_pipeline.py and await further instructions. -
🔒 Set up credentials
You need to provide your private API key with the
AuthorizationHTTP header for private routes, which can be obtained from your account settings or API dashboard.To get the appropriate API keys, please visit the original source at https://api.cleverpush.com/. 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 cleverpush_pipeline.pyIf your pipeline runs correctly, you’ll see something like the following:
Pipeline cleverpush load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset cleverpush_data The duckdb destination used duckdb:/cleverpush.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 cleverpush_pipeline show -
🐍 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("cleverpush_pipeline").dataset() # get "hourly-statistics" table as Pandas frame data."hourly-statistics".df().head()