Build Flows

Systems atlas

Construction systems atlas: how each one connects

API style, authentication, webhooks, sandboxes and the objects that matter for 17 systems contractors run, checked against each vendor's own documentation. Unknowns are marked, not guessed.

Last verified October 2026. Confirm details with each vendor before you build.

Browse systems

17 of 17 systems

Connect any two systems

Pick a pair to see what usually moves between them, who should own each record, and where to start.

Procore ↔ Viewpoint Vista

Objects that usually sync

  • Jobs / projects
  • Vendors / companies
  • Cost codes and cost types
  • Budgets
  • Commitments
  • Change orders
  • AP invoices
  • Actual costs

Direction and ownership

  • Accounting usually owns jobs, vendors and cost codes; they flow into project management.
  • Commitments and change orders are typically created in project management and pushed to accounting on approval.
  • Actual costs flow from accounting back to project management or into a reporting model.

Use case: Procore and Vista integration →

Comparison matrix

The short version. Each system page has the detail and the sources.

Procore

API style
REST
Auth
OAuth 2.0 (auth code, DMSA)
Webhooks / events
Yes (v4.0)
Sandbox
Yes, free

Autodesk Construction Cloud

API style
REST (APS)
Auth
OAuth 2.0 (2- and 3-legged)
Webhooks / events
Yes
Sandbox
APS free tier

Trimble ProjectSight

API style
REST (OpenAPI, .NET SDK)
Auth
Trimble Identity OAuth 2.0
Webhooks / events
Not documented
Sandbox
Not confirmed

Trimble Connect

API style
REST (+ BCF API)
Auth
OAuth 2.0 auth code + PKCE
Webhooks / events
None (poll)
Sandbox
Not confirmed

Viewpoint Vista

API style
REST (App Xchange)
Auth
API key
Webhooks / events
Via App Xchange flows
Sandbox
Paid test environment

Trimble Spectrum

API style
SOAP web services
Auth
Authorization ID + Basic / OAuth
Webhooks / events
Not documented
Sandbox
Not confirmed

Sage 300 CRE

API style
On-prem REST + ODBC
Auth
Partner key + Windows login
Webhooks / events
None documented
Sandbox
Partner program only

Sage Intacct Construction

API style
REST + legacy XML
Auth
OAuth 2.0 / sender ID
Webhooks / events
Partial (Smart Events)
Sandbox
Add-on module

QuickBooks Online

API style
REST (+ GraphQL)
Auth
OAuth 2.0 auth code
Webhooks / events
Yes
Sandbox
Yes, 10 companies

CMiC

API style
REST
Auth
OAuth via IdP (Basic until 2027)
Webhooks / events
Yes
Sandbox
Customer test environments

Foundation Software

API style
REST (OpenAPI)
Auth
Subscription key + bearer token
Webhooks / events
Not yet confirmed
Sandbox
Yes, after approval

Oracle Primavera P6

API style
REST + SOAP + XER/XML files
Auth
Basic / OAuth (OCI only)
Webhooks / events
JMS eventing (on-prem)
Sandbox
None public

Microsoft Project

API style
Dataverse + schedule APIs; MPP/XML files
Auth
Entra ID (licensed user)
Webhooks / events
Via Power Automate
Sandbox
Power Platform sandbox env

HCSS HeavyJob & HeavyBid

API style
REST
Auth
OAuth 2.0 client credentials
Webhooks / events
Yes
Sandbox
Partners only

HubSpot

API style
REST
Auth
OAuth 2.0 / static token
Webhooks / events
Yes
Sandbox
Free test accounts

Salesforce

API style
REST, SOAP, Bulk, Pub/Sub
Auth
OAuth 2.0 (External Client App)
Webhooks / events
CDC + platform events
Sandbox
Free Developer Edition

Microsoft Fabric & Power BI

API style
REST + OneLake (ADLS)
Auth
Entra ID / service principal
Webhooks / events
n/a (destination)
Sandbox
60-day trial

Choosing how to connect them is a separate question: compare connectors, iPaaS, in-house and specialist builds, or map your whole stack.

Frequently asked questions

Where does this information come from?

Each system page lists the official developer documentation it was checked against, plus our own build notes where we have integrated the system. Where a vendor doesn't publish something, such as rate limits, the page says so instead of guessing.

Why do some entries say “Confirm with vendor”?

Some construction vendors document their APIs only to customers or partners, or behind a login. We only state what a public official source or our own build work supports, and mark the rest so you know what to ask.

How current is it?

Every entry was last verified in October 2026. Vendors change APIs, limits and partner programs regularly, so check the linked documentation before you design around a detail.

Next step

Connecting two of these?

Tell us which systems and what should move between them. We'll say what we'd build, what we'd buy, and what to check first.

Prefer email? charley@buildflows.ai