ApivomApivom
Get Demo

Autodesk APS Secure Service Account Connector

Autodesk Platform Services' Secure Service Account (SSA) API — create and manage service-account identities and their signing keys, then exchange a signed assertion for an access token — registered in Apivom Atlas as 10 routes: the non-interactive identity layer for server-side APS integrations.

What you can do

  • Service accounts: create, list, read, update and delete under your APS application
  • Keys per service account: create, list, rotate (update) and delete the public keys the account signs with
  • Token: exchange a JWT assertion signed with a service-account key for a scoped APS access token — no user login, no shared secret in the request
  • 10 routes (3 read-only) on developer.api.autodesk.com, documented in the AI integration guide (llms.txt)

Use cases

  • Unattended access to ACC projects — Create a service account, invite it to the projects a nightly sync must read, and let the job mint its own tokens without a user session.
  • Key rotation without downtime — Register a new key, switch signing to it, then delete the old key — the service account and its project memberships stay unchanged.

Secure Service Account solves a practical problem of Autodesk Platform Services: most Autodesk Construction Cloud and Data Management data is only reachable with a three-legged token, which normally needs a human to sign in. SSA lets an application create service accounts — machine identities with their own Autodesk user id — that an account administrator can invite into ACC projects like any member. Each service account holds one or more public keys; the application signs a short-lived JWT assertion with the matching private key and posts it to the token endpoint to receive an access token with the requested scopes. Management routes create, read, update and delete service accounts and their keys, using two-legged tokens with the application:service_account scopes. Apivom Atlas catalogues all 10 routes, 3 read-only, with the APS credential contract and the AI integration guide (llms.txt), logging each call per tenant; private keys never pass through Atlas. No Apivom product workflow uses APS today; the connector is the building block for any unattended ACC sync, 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.

How is this different from a two-legged token?

A two-legged token identifies the application and only reaches app-owned resources such as OSS buckets. A service-account token identifies a machine user that can be a member of ACC or BIM 360 projects, so it reaches the same hubs, folders and issues a signed-in user would — without the sign-in.

Where does the private key live?

With the caller. Autodesk only stores the public key; the application keeps the private key, signs the assertion locally and sends the assertion to the token route. Apivom Atlas forwards that call and stores nothing.

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.