BuildingConnected & Trade Tapp Python API Docs | dltHub

BuildingConnected and TradeTapp APIs allow developers to extract and manage preconstruction data, including bidding, qualification, and financial information, through Autodesk Platform Services. The REST API base URL is https://developer.api.autodesk.com/construction/buildingconnected/v2 and all requests require an OAuth 2.0 Bearer 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 BuildingConnected & Trade Tapp data in under 10 minutes.

---

What data can I load from BuildingConnected & Trade Tapp?

Here are some of the endpoints you can load from BuildingConnected & Trade Tapp:

---

How do I authenticate with the BuildingConnected & Trade Tapp API?

The API uses Autodesk Platform Services (APS) OAuth 2.0 authentication. Requests require an Authorization header with a Bearer token obtained via a 3-legged OAuth flow.

1. Get your credentials

To obtain API credentials, you must first have an active, paid subscription to BuildingConnected or TradeTapp. Please contact your company's Account Executive or Customer Success Manager to request API access. Once enabled, navigate to your Account Settings within the BuildingConnected or TradeTapp application interface to generate your specific API credentials. Note that the APIs utilize the Autodesk Platform Services (APS) ecosystem for authentication.

2. Add them to .dlt/secrets.toml

Copy
[sources.buildingconnected_trade_tapp_source]
aps_client_id = "your_client_id_here"
aps_client_secret = "your_client_secret_here"
# Note: These APIs typically use OAuth 2.0 3-legged authentication (Authorization Code flow) # which requires user-level login rather than static service-level API keys.

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:

Copy
uv venv && source .venv/bin/activate
uv pip install "dlt[workspace]"

1. Install the dlt AI harness:

Copy
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:

Copy
dlthub 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 BuildingConnected & Trade Tapp 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:

Copy
python buildingconnected_trade_tapp_pipeline.py

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

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

Inspect your pipeline and data:

Copy
dlt pipeline buildingconnected_trade_tapp_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 /v2/opportunities and /v2/vendors from the BuildingConnected & Trade Tapp API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

Copy
import dlt
from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources

@dlt.source
def buildingconnected_trade_tapp_source(access_token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://developer.api.autodesk.com/construction/buildingconnected/v2",
            "auth": {"type": "bearer", "token": access_token},
        },
        "resources": [
            {"name": "projects", "endpoint": {"path": "projects"}},
            {"name": "bids", "endpoint": {"path": "bids"}}
        ],
    }
    yield from rest_api_resources(config)


def get_data() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="buildingconnected_trade_tapp_pipeline",
        destination="duckdb",
        dataset_name="buildingconnected_trade_tapp_data",
    )
    load_info = pipeline.run(buildingconnected_trade_tapp_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):

Copy
import dlt

data = dlt.pipeline("buildingconnected_trade_tapp_pipeline").dataset()
sessions_df = data.projects.df()
print(sessions_df.head())

SQL (DuckDB example):

Copy
SELECT * FROM buildingconnected_trade_tapp_data.projects LIMIT 10;

In a marimo or Jupyter notebook:

Copy
import dlt

data = dlt.pipeline("buildingconnected_trade_tapp_pipeline").dataset()
data.projects.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 BuildingConnected & Trade Tapp data to?

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

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.

Copy
dlthub ai toolkit data-exploration install
dlthub ai toolkit dlthub-platform install

• How to deploy a pipeline
• How to explore your data in marimo Notebooks
• How to query your data in Python with dataset
• Join the dlt community on Slack