Load Repliers data in Python using dltHub

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

In this guide, we'll set up a complete Repliers 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 repliers_source(access_token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.repliers.io/",
            "auth": {
                "type": "bearer",
                "token": access_token,
            },
        },
        "resources": [
            places,,agents,,clients
            ],
    }
    [...]
    yield from rest_api_resources(config)


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

Places: Manage and retrieve information about various locations.
Agents: Access details related to agents.
Clients: Handle client information and interactions.
Members: Manage member-related data.
Offices: Retrieve information about different offices.
Listings: Access property listings and related data.
Messages: Manage communication messages.
Webhooks: Set up and manage webhooks for real-time updates.
Searches: Handle search operations for listings and other entities.
Favorites: Manage favorite listings for clients.
Buildings: Retrieve data about specific buildings.
Locations: Access various location data.
Estimates: Manage and retrieve estimates for properties.
Brokerages: Access information about brokerages.
Tags: Manage client tags for better categorization.

You will then debug the Repliers 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 Repliers support.
```
dlt init dlthub:repliers 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 Repliers API, as specified in @repliers-docs.yaml 
Start with endpoints places and  and skip incremental loading for now. 
Place the code in repliers_pipeline.py and name the pipeline repliers_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 repliers_pipeline.py and await further instructions.

🔒 Set up credentials

The Repliers API requires an API key for authentication, which must be included in the request headers.

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

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


Pipeline repliers load step completed in 0.26 seconds
1 load package(s) were loaded to destination duckdb and into dataset repliers_data
The duckdb destination used duckdb:/repliers.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 repliers_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("repliers_pipeline").dataset()
# get lace table as Pandas frame
data.lace.df().head()
```

Running into errors?

There are limitations for test accounts including a cap on results per page (15), use of fixed images for listings, scrambled listing information, and potential restrictions on certain API endpoints. Additionally, various HTTP response codes indicate specific issues such as authentication failures, permission issues, poorly formatted requests, and rate limiting.

Extra resources:

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