BridgeFT WealthTech API Python API Docs | dltHub
Build a BridgeFT WealthTech API-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
BridgeFT WealthTech API is an API-first wealth management infrastructure framework that provides access to multi-custodial data and financial application services. The REST API base URL is https://api.bridgeft.com/v2 and all requests require 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 BridgeFT WealthTech API data in under 10 minutes.
What data can I load from BridgeFT WealthTech API?
Here are some of the endpoints you can load from BridgeFT WealthTech API:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| accounts | /v2/account-management/accounts | GET | data | List all accounts |
| account_by_id | /v2/account-management/accounts/{id} | GET | Get single account by ID | |
| positions | /v2/market-data/source-positions | GET | data | List all position records |
| transactions | /v2/market-data/source-transactions | GET | data | List all transaction records |
| securities | /v2/market-data/securities | GET | data | List all available securities |
How do I authenticate with the BridgeFT WealthTech API API?
BridgeFT WealthTech API uses OAuth2.0 authentication; clients must first exchange machine-to-machine (M2M) credentials (client_id and client_secret) via a Basic Auth POST request to obtain a JWT access token, which is then passed in the 'Authorization' header as 'Bearer '.
1. Get your credentials
BridgeFT provides credentials via their internal management process. You must contact your BridgeFT Account Manager to request access to the developer platform. Once onboarded, BridgeFT will provide you with two pairs of credentials: a client_id and a client_secret for the sandbox environment, and a separate set for the production environment. To authenticate, Base64 URL-encode the string <CLIENT_ID>:<CLIENT_SECRET> and pass it in the Authorization header as Basic <ENCODED_STRING> when requesting an OAuth token from the /oauth2/token endpoint.
2. Add them to .dlt/secrets.toml
[sources.bridgeft_wealthtech_api_source] bridgeft_client_id = "your_client_id_here" bridgeft_client_secret = "your_client_secret_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 BridgeFT WealthTech API 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 bridgeft_wealthtech_api_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline bridgeft_wealthtech_api_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset bridgeft_wealthtech_api_data The duckdb destination used duckdb:/bridgeft_wealthtech_api.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 /oauth2/token and /account-management/accounts/filter from the BridgeFT WealthTech API 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 bridgeft_wealthtech_api_source(token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.bridgeft.com/v2", "auth": {"type": "bearer", "token": token}, }, "resources": [ {"name": "accounts", "endpoint": {"path": "account-management/accounts", "data_selector": "data"}}, {"name": "positions", "endpoint": {"path": "market-data/source-positions", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="bridgeft_wealthtech_api_pipeline", destination="duckdb", dataset_name="bridgeft_wealthtech_api_data", ) load_info = pipeline.run(bridgeft_wealthtech_api_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("bridgeft_wealthtech_api_pipeline").dataset() sessions_df = data.accounts.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM bridgeft_wealthtech_api_data.accounts LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("bridgeft_wealthtech_api_pipeline").dataset() data.accounts.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 BridgeFT WealthTech API 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 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 BridgeFT WealthTech API?
Request dlt skills, commands, AGENT.md files, and AI-native context.