Autodesk Construction Cloud API Guide for Contractors

One-line verdict: A genuinely strong API — buried under four layers of setup, starting with the fact that there is no API key inside ACC at all. Openness: 3 / 5 — rated 3 because Autodesk documents broad REST APIs with real webhooks through Autodesk Platform Services, but access stacks a paid subscription, per-module licences, a separately registered developer app, and admin provisioning before anything connects. (Name note: Autodesk is folding ACC into Autodesk Forma — its blog states ACC becomes part of Forma and Docs becomes Forma Data Management, so expect the labels to keep moving.)

The connection that works

Rung 1 — Direct connection, through a side door called APS. ACC’s APIs don’t live in ACC. They live in Autodesk Platform Services (APS — formerly Forge), with public OpenAPI specifications. The route your admin actually takes: register an app in the APS developer portal and get a Client ID and Secret; then an ACC account admin provisions that app into your account (Account Admin → Custom Integrations); only then can it touch your projects. Sign-in is OAuth 2.0 — two-legged for server-to-server work, three-legged when acting for a user — with scopes like data:read and data:write. No admin, no connection: the provisioning step is not optional paperwork.

Verified surface: Projects — list/get and a documented create endpoint; Companies — documented read; Issues — create, read, and update, the long-standing core of the ACC API families. API families also exist for RFIs, submittals, files and folders, assets, and checklists — but per-endpoint write verbs for RFIs and submittals were not individually re-verified in our pass, so they’re flagged below rather than assumed. ACC works in users, companies, and roles — there is no CRM-style contacts object to sync.

Webhooks: real and documented for Issues — events like issue.created, issue.updated, and issue.deleted (with newer beta events for comments and attachments). One permission wrinkle, from Autodesk’s own post: only users with Project Admin permissions can create Issues webhooks.

Bridge apps: no native Zapier or Make app for ACC was verified. What Autodesk itself documents is a generic pattern — APS webhooks received by a Zapier “Catch Hook” — which is a webhook-to-bridge workaround, not an ACC Zapier app.

Can automate

• Issue-driven workflows — an issue created or updated in the field can fire a webhook and start the office follow-up, the RFI trail, or the client update automatically.
• Project provisioning — projects can be created and read through the API, so your other systems can spin up matching records when a job starts.
• Company directory reads — the companies working across your account can be pulled into reporting and coordination tools.
• File and document flows — the APS families around files and folders are the documented backbone for moving drawings and documents between systems (verify the specific endpoints per use case).

Can’t automate

• Cost and invoice writes — UNVERIFIED. A Cost Management API family exists; no specific invoice, payment, or budget write endpoint was verified from a vendor page in our pass. No money-write claim should be quoted yet.
• Company creation — UNVERIFIED. Companies read is documented; create/import was not verified.
• RFI and submittal write verbs, endpoint by endpoint — UNVERIFIED in this pass (the families exist; the specific verbs weren’t re-verified).
• A rate-limit number — UNVERIFIED. No single ACC-wide rate limit was verified from an APS page; don’t let anyone quote you one.
• A “customer reviews” connection — trap alert: ACC has a “Reviews” API family, and it means design and document review workflows on project files. It is not customer reviews. Like every platform here, ACC has no verified customer-reviews API.

Hidden gate: There is no API key inside ACC — your admin has to register a separate Autodesk developer app and then approve it into your account. Four gates stack: subscription, the module licence for the data you want, the APS app, and the admin provisioning. Budget all four.

Build fit — what this platform supports well

• Field-to-office issue flow — the strongest fit: Issues are the verified heart of this API, webhooks included.
• Project setup automation — documented project create/read makes ACC a workable hub for bigger GC workflows.
• Invoice Chase / AR — not yet: cost writes are UNVERIFIED, so AR automation keys off your accounting system, not ACC.
• Review Engine — like every platform here, ACC has no verified customer-reviews API (its “Reviews” are document reviews), so the review ask runs on our system triggered by a job-completion signal.

What this means for your shop

If you’re a bigger GC or design-build shop already living in Autodesk, the capability is real and the ceiling is high — especially around issues and project files. But nothing about it is a quick connect: it starts with an APS app and an admin who provisions it, under licences you may need to extend. Shops that already own ACC and have that admin will experience a 4; shops buying in cold should price the gates in before pricing the automation.