Autodesk Platform Services (APS / Forge) — scaffold only

SDK + auth + viewer-manifest stubs are wired. Live API calls activate when the env vars below are set and the feature flag is on.

Deferred behind operator decision. APS / Forge integration sits dormant until the Models register has real uploads and the operator confirms the AUD spend on Autodesk entitlements. The scaffold stays in place so it can be flipped on without rebuilding — same pattern as the Bluebeam stub.

Current configuration

APS_ENABLED: off
APS_CLIENT_ID: missing
APS_CLIENT_SECRET: missing
APS_BASE_URL: https://developer.api.autodesk.com
APS_REGION: US

Overall: scaffold only

Connection test

Connection test returned status 501.

APS_ENABLED is off or APS_CLIENT_ID/APS_CLIENT_SECRET are unset. Real 2-legged token acquisition is deferred until the integration is unblocked by the operator.

Env-var setup

Provision a 2-legged Forge app at aps.autodesk.com with the data:read and viewables:read scopes, then set these on the staging Container App (or local .env.local):

APS_ENABLED=1
APS_CLIENT_ID=<your forge client id>
APS_CLIENT_SECRET=<your forge client secret>
APS_BASE_URL=https://developer.api.autodesk.com   # optional
APS_REGION=US                                      # or EMEA

Restart the web app after setting the values. The flag defaults to off so a forgotten secret can't accidentally activate the integration in production.

Stubbed endpoints

POST /api/v1/integrations/aps/auth → 501 until enabled
GET /api/v1/integrations/aps/auth → status probe (always 200)
GET /api/v1/integrations/aps/viewables/{urn} → 501 until enabled

Where the viewer lives

The Models register at /projects/{id}/models owns the upload + metadata side. The viewer shell lives separately at /projects/{id}/bim so the register stays useful even with this integration off.