VaultRE Python API Docs | dltHub
Build a VaultRE-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
VaultRE API provides access tokens for integration; API keys are rate-limited to 10 requests per second and 10,000 per day. For aggregator API, use Secret Key and JWT token for authorization. For assistance, email api@vaultre.com.au. The REST API base URL is https://ap-southeast-2.api.vaultre.com.au/api/v1.3 and All requests require X-Api-Key header and an Authorization: Bearer access token..
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 pip install "dlt[workspace]" 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:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| properties | /properties | GET | Retrieve a list of properties for the account | |
| residential_properties | /properties/residential/sale | GET | Retrieve a list of residential sale properties | |
| contacts | /contacts | GET | Retrieve a list of contacts | |
| scopes | /scopes | GET | Retrieve list of scopes assigned to the bearer token | |
| event_stream | /eventStream | GET | Poll the event stream | |
| properties_photos | /properties/{id}/photos | GET | Retrieve a list of photos for a property | |
| integrator_accounts | /integrator/accounts | GET | Retrieve a list of accounts linked to this integrator | |
| search_properties_address | /search/properties/address | GET | Search for properties by address | |
| suburbs | /suburbs | GET | Retrieve a list of suburbs for the user's country | |
| user | /user | GET | Retrieve information about the authenticated user |
How do I authenticate with the VaultRE API?
All requests must include X-Api-Key: {your API key} and Authorization: Bearer {client access token}. Both headers are required (X-Api-Key identifies the integrator; Authorization bearer token grants access to a specific account).
1. Get your credentials
- Register as an integrator via VaultRE (see https://resources.vaultre.com.au/api-integrations). 2) VaultRE will provide you with an API Key (integrator key). 3) Your customer (VaultRE client) must create an Access Token in Office Integrations -> Third-Party Access -> Create Token and provide it to you. 4) Use X-Api-Key with your integrator API Key and Authorization: Bearer {access_token} when calling the API.
2. Add them to .dlt/secrets.toml
[sources.vaultre_source] api_key = "your_api_key_here" access_token = "your_access_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 venv && source .venv/bin/activate uv pip install "dlt[workspace]"
1. Install the dlt AI Workbench:
dlt 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:
dlt ai toolkit rest-api-pipeline install
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:
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:
dlt pipeline vaultre_pipeline 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 properties and contacts 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": "api_key", "api_key": api_key, }, }, "resources": [ {"name": "properties", "endpoint": {"path": "properties"}}, {"name": "contacts", "endpoint": {"path": "contacts"}} ], } 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.properties.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM vaultre_data.properties LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("vaultre_pipeline").dataset() data.properties.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:
| Destination | Example 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 Workbench:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-runtime— Deploy, schedule, and monitor your pipeline in production.
dlt ai toolkit data-exploration install dlt ai toolkit dlthub-runtime install
Was this page helpful?
Community Hub
Need more dlt context for VaultRE?
Request dlt skills, commands, AGENT.md files, and AI-native context.