Subscribe to Events with a Signed Webhook
A 5-step recipe with Autodesk. We can help you get access.
Recipe · 5 steps
Subscribe to Events with a Signed Webhook
with Autodesk · Webhook & Event Subscription Management
Stand up a signed, folder-scoped webhook subscription.
- Discover which event systems currently accept webhook subscriptions rather than hardcoding a system string that may be retired.
- List the events the chosen system emits, confirming the event to subscribe to is real before a hook is created against it.
- Install the secret token Autodesk signs callback payloads with. Done before the hook exists so that every callback the hook ever fires is signed.
- Create the hook, scoped to a single folder so the callback endpoint is not flooded with events from the whole hub. autoReactivateHook keeps the subscription alive through a transient outage of the callback endpoint.
- Read the hook back to confirm it is active and pointed at the intended callback URL and scope.
What you'll need to have ready
- system: The event system to subscribe within (e.g. "data", "derivative", "adsk.c4r").
- event: The event type to subscribe to (e.g. "dm.version.added", "extraction.finished").
- callbackUrl: The HTTPS endpoint Autodesk POSTs callbacks to.
- secretToken: Secret used to sign callback payloads. Arrives on callbacks in the x-adsk-signature header and must be verified before trusting a payload.
- folderUrn: The folder URN to scope the subscription to.
- filter: Optional JSON filter expression narrowing which events fire the hook (e.g. by file extension).
For your developer
Arazzo workflow autodesk:subscribe-to-events, 5 operations: getSystems → getSystemEvents → createToken → createHook → getHook. Specs on APIs.io.