ApivomApivom
Get Demo

Autodesk APS Model Derivative Connector

Autodesk Platform Services' Model Derivative API — translate design files into viewer formats and other outputs, read manifests and thumbnails, extract object trees and properties — registered in Apivom Atlas as 12 routes for tenants that need CAD and BIM data readable outside the authoring tool.

What you can do

  • Start translation jobs (SVF2 for the viewer, OBJ, STL, IFC and more) and follow the manifest until derivatives are ready
  • Metadata: list model views, read the object tree and property sets of a view, run property queries on large models
  • Supported input/output formats, thumbnails, signed cookies for derivative downloads, manifest deletion, reference declarations for assemblies
  • 12 routes (7 read-only) on developer.api.autodesk.com, documented in the AI integration guide (llms.txt)

Use cases

  • Show the model next to the deal — Translate the customer's file to SVF2 once and embed the Autodesk Viewer in your portal or CRM so sales and support see the actual design.
  • Quantities and properties for estimating — Read the object tree and element properties of a Revit or IFC model to feed takeoff, costing or procurement without a desktop seat.
  • Automatic format conversion — Produce STL, OBJ or IFC derivatives on upload so downstream manufacturing and analysis tools get the format they expect.

Model Derivative turns a design file — Revit, Inventor, AutoCAD, Navisworks and dozens of other formats — into something other systems can use: the SVF2 derivatives the Autodesk Viewer renders, exchange formats such as OBJ, STL or IFC, and the structured metadata behind the model. The flow is: upload the file to OSS, declare references for multi-file assemblies, post a translation job for the file's URN, poll the manifest until the derivatives are complete, then read the thumbnail, the model views, the object tree and the properties of every element — with a query endpoint for models too large to download in one response. Signed cookies protect derivative downloads; a manifest can be deleted to free the translation. Access is two-legged for app-owned files or three-legged for files in a user's ACC or Fusion project. Apivom Atlas catalogues all 12 routes, 7 read-only, with the APS credential contract and the AI integration guide (llms.txt), logging each call per tenant. No Apivom product workflow uses APS today; the connector is available to tenants that embed viewers or extract quantities from models, 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 do I know a translation is finished?

Post the job, then poll the manifest for the URN: its status moves from pending to inprogress to success (or failed), and each derivative lists its own progress. Only read metadata and properties after the manifest reports success.

Does translation cost anything on Autodesk's side?

Yes — Autodesk meters Model Derivative in cloud credits on the APS application that owns the token, with some output formats (such as SVF2) free of charge. Check the current APS pricing for your formats; Apivom adds no charge.

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.