VaultRE Python API Docs | dltHub

Build a VaultRE-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.

Last updated:

VaultRE is a real estate CRM platform providing a REST API for integrating third-party applications with agency and account data. The REST API base URL is https://ap-southeast-2.api.vaultre.com.au/api/v1.3 and all requests require both an integrator-level API key in the X-Api-Key header and a bearer token in the Authorization header.

dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv add "dlt[hub]" and start loading VaultRE data in under 10 minutes.


What data can I load from VaultRE?

Here are some of the endpoints you can load from VaultRE:

ResourceEndpointMethodData selectorDescription
contactscontactsGETitemsRetrieve a list of contacts
propertiespropertiesGETitemsRetrieve a list of properties
buildingsbuildingsGETitemsRetrieve a list of buildings
event_streameventStreamGETPoll the event stream
integrator_accountsintegrator/accountsGETitemsRetrieve a list of accounts linked to this integrator

How do I authenticate with the VaultRE API?

All requests require two headers: 'X-Api-Key' for the integrator API key and 'Authorization' for the bearer token, which follows the format 'Bearer [token]'. For the core API, the bearer token is a customer-granted access token, while integrator/aggregator endpoints require a self-signed HS512 JWT token in the same 'Authorization' header.

1. Get your credentials

VaultRE does not provide a self-service dashboard for generating API credentials. To obtain your integrator API key, you must register as a developer or third-party integrator by contacting VaultRE at api@vaultre.com.au. Once your integration request is reviewed and approved, VaultRE will issue your unique API key. For individual customer access tokens, these are either generated by the client within their VaultRE account (Office Integrations > Third-Party Access > Create Token) or via an OAuth2 authorization flow.

2. Add them to .dlt/secrets.toml

[sources.vaultre_source] api_key = "your_integrator_api_key_here" access_token = "your_client_provided_access_token_or_oauth_token_here"

dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.


How do I set up and run the pipeline?

Set up a virtual environment and install dlt:

uv init uv add "dlt[hub]"

1. Install the dlt AI harness:

uv run dlthub ai init --agent <your-agent> # <agent>: claude | cursor | codex

This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →

2. Install the rest-api-pipeline toolkit:

uv run dlthub ai toolkit install rest-api-pipeline

This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →

3. Start LLM-assisted coding:

Use /find-source to load data from the VaultRE API into DuckDB.

The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.

4. Run the pipeline:

uv run python vaultre_pipeline.py

If everything is configured correctly, you'll see output like this:

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

Inspect your pipeline and data:

uv run dlthub show

This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.


Python pipeline example

This example loads contacts and properties from the VaultRE API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def vaultre_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://ap-southeast-2.api.vaultre.com.au/api/v1.3", "auth": {"type": "bearer", "token": api_key}, }, "resources": [ {"name": "contacts", "endpoint": {"path": "contacts", "data_selector": "items"}}, {"name": "properties", "endpoint": {"path": "properties", "data_selector": "items"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="vaultre_pipeline", destination="duckdb", dataset_name="vaultre_data", ) load_info = pipeline.run(vaultre_source()) print(load_info)

To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.


How do I query the loaded data?

Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.

Python (pandas DataFrame):

import dlt data = dlt.pipeline("vaultre_pipeline").dataset() sessions_df = data.contacts.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM vaultre_data.contacts LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("vaultre_pipeline").dataset() data.contacts.df().head()

See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.


What destinations can I load VaultRE data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample value
DuckDB (local, default)"duckdb"
PostgreSQL"postgres"
BigQuery"bigquery"
Snowflake"snowflake"
Redshift"redshift"
Databricks"databricks"
Filesystem (S3, GCS, Azure)"filesystem"

Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.


Next steps

Continue your data engineering journey with the other toolkits of the dltHub AI harness:

  • data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
  • dlthub-platform — Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform

Was this page helpful?

Community Hub

Need more dlt context for VaultRE?

Request dlt skills, commands, AGENT.md files, and AI-native context.