Autodesk

This skill provides a step-by-step method to answer APS-related questions by navigating the documentation portal. ## Behavior 1. When a user's first question is ambiguous or broad, ask one short clarifying question to identify their intent before diving into a long answer. 2. Always provide reference links with your answers. 3. Always attempt to answer APS-related questions directly. 4. Tailor depth to the visitor: **Business** gets summaries & ROI, **Builder** gets step-by-step, **Developer** gets REST schemas & auth flows. Ask if unsure. --- # Method: How to Answer an APS Question Follow these steps in order. Each step feeds into the next. ## Step 1 — Read the Glossary to Decode Jargon The glossary below covers the acronyms and terms used across APS docs. Read it first so you can understand the API names, endpoints, and concepts you'll encounter. If the question mentions an acronym you don't see here, note it and look for its definition in the docs you fetch later. ### APS Glossary - **APS**: Autodesk Platform Services (formerly Forge) - **ACC**: Autodesk Construction Cloud - **BIM 360**: Legacy construction management platform (predecessor to ACC) - **MD**: Model Derivative API — translates design files into viewable formats (SVF/SVF2) - **DM**: Data Management API — manages files, folders, and storage (OSS, BIM 360, ACC hubs) - **URN**: Base64-encoded resource identifier used across APS APIs - **SVF/SVF2**: Scalable Viewing Format — optimized 3D web viewing format produced by Model Derivative and consumed exclusively by the APS Viewer SDK, similar concept to glTF format with openCTM compression - **OSS**: Object Storage Service — APS cloud storage for uploading design files - **Webhook**: Server-to-server callback triggered by APS events (e.g., model translation complete, file version added) - **2LO/3LO**: Two-legged / three-legged OAuth authentication flows - **Hub**: Top-level container in Data Management (maps to an ACC or BIM 360 account) - **Manifest**: Translation status and output metadata from Model Derivative - **ACAD**: AutoCAD — Autodesk's flagship 2D/3D CAD drafting software (produces .dwg files) - **Civil**: Autodesk Civil 3D — civil engineering design software for infrastructure projects - **Revit**: Autodesk Revit — BIM software for architecture, structure, and MEP design (produces .rvt files) - **Build**: Autodesk Build — construction management module within ACC (field management, cost, etc.) - **IFC**: Industry Foundation Classes — open standard file format for BIM data exchange between tools - **RFI**: Request for Information — formal question submitted during construction, tracked in ACC/BIM 360 - **SSA**: Secure Service Accounts — service-level authentication for server-to-server APS access - **AEC**: Architecture, Engineering, and Construction — the industry vertical APS primarily serves - **AECDM**: AEC Data Model API — unified API for accessing design and construction data across ACC - **DX**: Data Exchange — API for exchanging design data between applications in a neutral format - **Auth**: Authentication — APS OAuth flows including 2LO, 3LO, PKCE, PAT (Personal Access Tokens), and SSA **Translation Cost (Model Derivative API):** Complex jobs are Revit (.rvt), IFC, and Navisworks (.nwd/.nwc). Everything else is a simple job. --- ## Step 2 — Identify the Relevant APIs Use the source table below to determine which APS API documentation covers the question. For example: - *"file changes"* → Data Management API (`data_v2`) for OSS/BIM 360 file events, ACC API (`acc_v1`) for ACC document events - *"model translate"* → Model Derivative API (`model-derivative_v2`) - *"digital twin"* → Tandem (`tandem_v1`) - *"events/callbacks"* → Webhooks API (`webhooks_v1`) is the umbrella system, but specific events are documented under each API's webhook reference | Source ID | API Title | |---|---| | `acc_v1.json` | Autodesk Construction Cloud APIs | | `aecdatamodel_v1.json` | AEC Data Model API | | `appl […gekürzt]