ApivomApivom
Get Demo

Autodesk APS Authentication (OAuth2 v2) Connector

Autodesk Platform Services' Authentication API v2 — authorize, token, introspect, revoke, logout, JWKS keys, OpenID discovery and userinfo — registered in Apivom Atlas as the token layer every other APS connector depends on, for AEC, manufacturing and construction-tech tenants.

What you can do

  • OAuth2 v2 endpoints: authorize (three-legged), token (two- and three-legged, refresh), introspect, revoke, logout
  • OpenID Connect: well-known configuration, JWKS keys for token validation, userinfo for the signed-in Autodesk user
  • Eight routes (five read-only) on developer.api.autodesk.com, documented in the AI integration guide (llms.txt)
  • Scopes decide what the token may reach — data:read, data:write, account:read and more — across Data Management, OSS, Model Derivative, Webhooks and ACC

Use cases

  • Sign users in with Autodesk ID — Run the three-legged flow so your application can reach a user's ACC hubs and projects with their own permissions, and keep the session alive with refresh tokens.
  • Service tokens for background jobs — Mint two-legged tokens with exactly the scopes a translation or webhook job needs, and validate them locally with the JWKS keys.

Autodesk Platform Services (formerly Forge) is the cloud API platform behind Autodesk Construction Cloud, BIM 360, Fusion and the viewer, and every call into it starts with Authentication v2. Two-legged tokens (client credentials) let an application act on its own data — buckets, translations, webhooks; three-legged tokens (authorization code) let it act for a signed-in Autodesk user and reach their hubs and projects; refresh tokens keep the latter alive. The API also offers introspection and revocation, logout, the OpenID well-known document and JWKS keys for validating tokens locally, and a userinfo endpoint. Apivom Atlas catalogues all eight routes with the APS credential contract — client id, client secret and the scope list — and the AI integration guide (llms.txt); in practice the token exchange is done by the caller and the resulting Bearer is sent to the other APS connectors. No Apivom product workflow uses APS today — the connector family is available to tenants building design, BIM or construction integrations, 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.

Two-legged or three-legged — which do I need?

Two-legged (client credentials) for resources your application owns: OSS buckets, Model Derivative jobs, webhooks. Three-legged (authorization code) whenever you read or write a user's or account's data in ACC, BIM 360 or Fusion Team. Many integrations use both.

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.