Integration guide

Autodesk Construction Cloud and Viewpoint Vista integration

Vista owns jobs, vendors and the phase list; ACC Cost Management sends approved contracts and change orders back for posting. Both sides publish REST APIs, but they behave differently: ACC calls fail until the customer admin adds your app, and Vista reads come from an hourly cache while writes are queued actions.

Book a 30-minute call Send a short brief

System facts last verified October 2026 against the vendors' documentation (sources below). Confirm details with Autodesk and Trimble before you build.

Autodesk ACC and Vista side by side

API style: Autodesk ACCREST/JSON through Autodesk Platform Services (APS).; VistaREST/JSON on the Trimble App Xchange platform. Reads are GETs against a cache; writes are POSTed actions such as add, replace, upsert and post.
Authentication: Autodesk ACCAPS OAuth 2.0: two-legged (client credentials) and three-legged (authorization code), plus Secure Service Accounts for server-to-server apps. A customer account admin must add your app's client ID under Account Admin > Custom Integrations.; VistaAn API key in the X-Application-Key header over HTTPS. Keys come through your Trimble sales representative; third-party vendors get their own scoped key from the customer.
Webhooks / events: Autodesk ACCYes, through the APS Webhooks API: Data Management events (such as new file versions) and issue events (created, updated, deleted and more), among others.; VistaNone in the API docs. Through App Xchange flows, creates, updates and deletes detected in the cache can trigger integration flows.
Rate limits: Autodesk ACCPublished per service and endpoint; for example, Cost Management allows 5,000 requests per minute overall, and Data Management endpoints mostly fall between 50 and 800 per minute per client ID. Exceeding a limit returns 429 with Retry-After.; Vista2,000 requests per minute per API key (rolling 60 seconds, subject to change); 429 with Retry-After when exceeded. Multi-record GETs return up to 1,000 records with continuation tokens.
Sandbox: Autodesk ACCAPS has a free tier covering cloud APIs, with monthly limits on select metered APIs. No separate construction sandbox confirmed; test in a project you control.; VistaTrimble says you can purchase and connect a test environment to your Vista test instance. No free developer program.
Exports and files: Autodesk ACCData Connector API: scheduled or one-time CSV extracts (ZIP), up to 50 projects per request, with files available for 30 days.; VistaAttachments download through a cache-file action that returns a download URL.
Marketplace / partners: Autodesk ACCAutodesk Developer Network (ADN); members can request rate-limit increases. App listing programs not confirmed.; VistaTrimble App Xchange.

Who owns what

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.

What syncs between Autodesk ACC and Vista

The typical shape for this pair. Every row is typical: confirm it against your configuration in discovery.

Arrows point from the system that sends to the system that receives. Dashed means it stays put.

Object	Direction	System of record	Typical frequency
Jobs → projects	Vista to Autodesk ACC	Vista (company plus job number)	Hourly
Typical frequency: Hourly. Notes: A Vista job number is only unique within a company, so key on company plus job. A closed job is a status change to mirror, not a delete.(Typical: confirm against your configuration.)
Vendors → companies	Vista to Autodesk ACC	Vista	Hourly
Typical frequency: Hourly. Notes: Create vendors in Vista first and reference the Vista vendor number in ACC; name matching creates duplicates.(Typical: confirm against your configuration.)
Phases and cost types → ACC budget codes	Vista to Autodesk ACC	Vista (standard phase list)	At job setup, then on change
Typical frequency: At job setup, then on change. Notes: Map Vista phases and cost types to ACC budget codes in a table accounting reviews, and reject unknown codes.(Typical: confirm against your configuration.)
Budgets	Vista to Autodesk ACC	Vista original estimate at award; ACC after	Once at setup
Typical frequency: Once at setup. Notes: Seed ACC budgets from Vista budget codes and original estimates. Changes after award go through ACC Cost Management.(Typical: confirm against your configuration.)
Contracts → subcontracts and POs	Autodesk ACC to Vista	Pick one: often drafted in ACC, posted in Vista	Every 15 minutes
Typical frequency: Every 15 minutes. Notes: Approved contracts only. Vista writes are async actions: store the action ID, poll for the result, and route failures to a person.(Typical: confirm against your configuration.)
Change orders	Autodesk ACC to Vista	ACC for approval; Vista for posted cost	Every 15 minutes
Typical frequency: Every 15 minutes. Notes: Approved only, landing as Vista SL change orders or approved change orders. Hold one whose contract hasn't synced yet.(Typical: confirm against your configuration.)
Actual cost	Vista to Autodesk ACC	Vista (job cost detail)	Daily
Typical frequency: Daily. Notes: Read from Vista's API cache, typically refreshed hourly, so plan comparisons around that lag.(Typical: confirm against your configuration.)
RFIs and issues	not synced	ACC	Not synced
Typical frequency: Not synced. Notes: Vista PM has RFIs and issues too. Syncing both creates two records of truth; keep them in ACC and join in reporting if needed.(Typical: confirm against your configuration.)

Directions, owners and frequencies are the typical pattern from our integration guides and mapping workbook. Confirm each one against your configuration in discovery.

Is a native connector enough?

We haven't confirmed a documented native connector for this pair. Check Trimble App Xchange (where Vista's API runs) and ask Autodesk for a partner connector first: if one moves the records you need with your cost structure and approvals, configure it. Build when the mapping needs governing, when failures need routing to a person, or when you also need cross-system reporting.

Compare native connectors with a custom build

Common gotchas

ACC calls fail until the customer's account admin adds your client ID under Account Admin > Custom Integrations (Forma Hub Admin in Autodesk's newer naming). Put it on the go-live checklist.
Some ACC admin endpoints accept two-legged tokens only, while user-scoped tools need three-legged ones. Pick the token type per endpoint.
Vista reads come from the App Xchange cache, typically refreshed hourly, so a read right after a write may not show it. Track your own action IDs instead of re-reading.
Trimble's eligibility docs name cloud-hosted Vista on Trimble Construction One, and the API is a paid add-on. On-premises customers should confirm with Trimble what their license allows.

Sources

Frequently asked questions

Can Autodesk Construction Cloud integrate with Viewpoint Vista?

Yes, through ACC's APIs on Autodesk Platform Services and the Vista API on Trimble App Xchange. Vista usually feeds jobs, vendors and phases to ACC, and approved contracts and change orders flow back for posting.

Why does my ACC integration get 403 errors?

Usually because the account admin hasn't added your client ID under Custom Integrations, or the endpoint needs a different token type (two-legged versus three-legged).

How fresh is Vista data in ACC?

Vista API reads come from a cache synced from the Vista database, typically every hour, and multi-record reads return up to 1,000 records per page. Expect up to about an hour of lag.

Next step

Connecting Autodesk ACC and Vista?

Bring one real job and the records you want to move. We'll walk through what syncs, who owns each record, and what to check first.

Book a 30-minute call Send a short brief