ApivomApivom
Get Demo

Autodesk APS Webhooks Connector

Autodesk Platform Services' Webhooks API — register callbacks on Data Management, Model Derivative, Autodesk Construction Cloud and Tandem events, list and manage hooks per system and event, and set the secret token Autodesk signs payloads with — registered in Apivom Atlas as 12 routes of plumbing for event-driven APS integrations.

What you can do

  • Hooks: create for one event or for every event of a system, list by application, by system or by event, read, update (status, filter, callback) and delete
  • Systems covered by APS Webhooks: data (Data Management file and folder events), derivative (translation finished), adsk.c4r (Revit Cloud Worksharing), autodesk.construction (ACC) and Tandem
  • Secret token: create, rotate and delete the per-application secret used for the x-adsk-signature header on deliveries
  • 12 routes (5 read-only) on developer.api.autodesk.com, documented in the AI integration guide (llms.txt)

Use cases

  • React to new file versions — Register dm.version.added on a project folder so your system picks up a new drawing issue the moment it lands, instead of scanning folders on a timer.
  • Chain translation to processing — Subscribe to extraction.finished and start property extraction or viewer caching exactly when Model Derivative reports the job complete.

APS Webhooks is infrastructure rather than a product feature: instead of polling Data Management or Model Derivative, an application registers a hook — a callback URL for a system and event, optionally with a scope such as a folder and a JSONPath filter — and Autodesk posts a payload whenever the event happens: a file version added or modified, a folder renamed, a translation finished, an ACC or Tandem change. The API creates hooks per event or per whole system, lists them for the application, a system or an event, reads, updates and deletes them, and manages the application's secret token so every delivery carries a verifiable x-adsk-signature. Hooks are owned by the token that created them: two-legged hooks are app-wide, three-legged hooks follow the user. Apivom Atlas catalogues all 12 routes, 5 read-only, with the APS credential contract and the AI integration guide (llms.txt), logging each call per tenant; the callbacks themselves go to the URL you register, not through Atlas. No Apivom product workflow uses APS today; this connector exists so a future ACC or Data Management integration can be event-driven, 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 do I verify a webhook delivery is really from Autodesk?

Create a secret token with the tokens route; Autodesk then signs every payload and sends the signature in the x-adsk-signature header. Recompute the HMAC over the raw body with your secret and compare before trusting the event.

Do the event payloads pass through Apivom Atlas?

No. Atlas only brokers the management calls — creating, listing, updating and deleting hooks and the secret. Autodesk delivers events straight to the callback URL you registered, which must be publicly reachable over HTTPS.

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.