Overview
Client-mode REST API connector for Autodesk Platform Services (APS): browse Data Management hubs, projects, folders, items and versions to show the latest design or drawing revision as a work instruction, read Model Derivative manifests and properties, subscribe webhooks to new versions, and query Fusion component properties and BOMs through the Manufacturing Data Model GraphQL API, with OAuth 2.0 tokens. This is one of the templates in the Autodesk Platform Services (Data Management, Manufacturing Data Model, Fusion) REST API app (autodesk-platform-services). Deploy it alongside the other connectors of that app when they depend on each other (for example a token connector plus an API connector).
Not yet verified against the live vendor API: No APS app credentials on the factory box (APS_CLIENT_ID / APS_CLIENT_SECRET unset) and no hub provisioned for such an app; the ready gate needs an authenticated live call (GetToken + ListHubs, or a broker MQTT round trip). Mock-server checks and unauthenticated probes of developer.api.autodesk.com (OIDC 200, JWKS 200, token 403 without client, every API path 401 without a token) do not clear the gate.
Auth
OAuth 2.0 (APS Authentication v2, POST /authentication/v2/token). Client authentication: Authorization: Basic base64(client_id:client_secret) from payload field authorization. GetToken = client_credentials (2-legged, scopes URL-encoded space-separated, e.g. data:read%20data:create); ExchangeCode = authorization_code (3-legged, after one browser sign-in to /authentication/v2/authorize); RefreshToken = refresh_token (rotates the refresh token). API events take authorization = ‘Bearer <access_token>’. Data Management / Model Derivative / Webhooks accept 2-legged (BIM 360 Docs / ACC after the account admin adds the app as an integration) or 3-legged; Fusion Team / BIM 360 Team / A360 data and all Manufacturing Data Model calls require 3-legged. Auth headers used by the template:Authorization: {value.json.authorization}.
Template parameters
BASE_ADDRESS default: https://developer.api.autodesk.com.
Events
Deploy
Get the template card (JSON withtemplate and metadata) from the broker, then deploy the connector:
BASE_ADDRESS already filled in:
-addRoute (do not include ADD METADATA).
Usage example
CallListHubs by publishing a JSON payload to its request topic, and read the reply on the response topic:

