ApivomApivom
Get Demo

Autodesk APS Construction Account Admin Connector

Autodesk Platform Services' Account Admin API for Autodesk Construction Cloud and BIM 360 — account projects, project users and roles, member and partner company directories, business units and bulk imports — registered in Apivom Atlas as 30 routes for construction-tech tenants that run many projects.

What you can do

  • Construction Admin v1: list and create account projects, read a project, list, add, update, remove and bulk-import project users
  • HQ v1 (BIM 360 Account Admin): account users and companies with search, create, update and import, business-unit structure, project companies and images
  • Per-user views: the products, projects and roles an account user holds
  • 30 routes (16 read-only) on developer.api.autodesk.com, documented in the AI integration guide (llms.txt)

Use cases

  • Provision a project when a deal closes — Create the ACC project, add the customer's team with the right roles and attach their company record — from the system where the contract was signed.
  • Keep the member directory in sync — Import or update account users and companies in bulk so the people and firms in ACC match your HR and vendor master data.
  • Audit who can reach what — Read a user's projects, roles and products across the account to answer access questions and clean up leavers.

Account Admin is the administrative layer of Autodesk Construction Cloud and BIM 360: the API behind the account-level Projects, Members and Companies pages. The Construction Admin v1 endpoints list and create projects on an account, read a project and manage its users — add one, import many, change roles and products, remove — plus per-user lookups of products, projects and roles. The older HQ v1 endpoints cover the account directory: users and companies with search, creation, update and bulk import, the business-unit structure, the companies attached to a project and company or project images. Access is three-legged with account:read or account:write scopes, so the API returns exactly what the signed-in account administrator may manage. Apivom Atlas catalogues all 30 routes, 16 of them read-only, with the APS credential contract and the AI integration guide (llms.txt), and logs each call per tenant. No Apivom product workflow uses APS today; the connector is available to tenants that need to provision projects and members from their own systems, and a product workflow is scoped per customer.

Authentication

Your Autodesk Platform Services app (client id + secret from aps.autodesk.com) and the scopes this API needs. The caller obtains the OAuth2 v2 token — two-legged for app-owned data, three-legged for a user's hubs — and sends it as Bearer; Apivom Atlas forwards, logs and stores nothing.

Frequently asked questions

Can I switch this connector on today?

The connector is registered in Apivom Atlas — every route is catalogued, the credential contract is published and the AI integration guide (llms.txt) is live — and your credential can be stored in Apivom Iris. Wiring it into a product workflow (sync, automation, notifications) is done per customer: tell us the use case and we scope it with you.

Construction Admin v1 or HQ v1 — which endpoints should I use?

Construction Admin v1 is the current API for Autodesk Construction Cloud projects and project users and is the one to build on. HQ v1 is the BIM 360 Account Admin API that still serves account users, companies and business units; both are catalogued so existing BIM 360 accounts keep working.

Which scopes does the token need?

account:read for lookups and account:write for creating projects, adding or updating users and companies; the token must be three-legged and belong to an account administrator of the ACC or BIM 360 account.

Does Apivom charge per API call for this connector?

No. Connectors are part of your Apivom tenant and are not metered in the Atlas portal. The vendor's own pricing, quotas and rate limits still apply to the account you connect — Apivom paces its calls to stay inside them and shows every call in your tenant's integration log.

Where are my credentials stored and who can see the traffic?

Apivom Atlas is a stateless gateway: it never stores vendor credentials or tokens. The Apivom product that connects keeps the credential encrypted in your tenant database, and every request and response is logged in your tenant only — your data is never shared across tenants.

More Atlas integrations

AI integration guide (llms.txt)

Machine-readable markdown — feed it to your AI assistant as integration instructions.