Exchanges and Mutations
What is an Exchange?
In Autodesk’s Data Exchange ecosystem, an Exchange is a curated, structured package of design data extracted from larger models (Revit, AutoCAD, IFC files) that can be shared independently across teams, tools, and workflows. Think of it as creating a focused subset of your complex model that contains only the information relevant to a specific purpose or team. Instead of sharing a massive Revit model when you only need the structural elements, you create a lightweight exchange containing just the model elements you need like beams, columns, and foundations.
Data Exchange workflow: From complex source models to targeted, shareable exchanges
Key Characteristics
| Feature | Description |
|---|---|
| Selective Extraction | Apply filters to extract only relevant objects, geometry, or metadata. For example: ifcClass = 'IfcDoor' from IFC files, category == 'Wall' from Revit models, or custom property-based filters. |
| Lightweight & Shareable | Extracted data is stored as a standalone exchange, significantly reducing file size and complexity while maintaining data integrity. |
| Versioned & Traceable | Each exchange has a unique ID and lifecycle, enabling updates, tracking, and reuse across project phases. For example, a “Structural Elements” exchange might evolve from initial design (version 1) to design development (version 2) to construction documents (version 3) as the project progresses. |
| Cross-Tool Interoperability | Exchanges can be consumed in multiple applications, for example: Autodesk products (Revit, Civil 3D, Inventor), third-party applications (Rhino, Grasshopper), and custom applications via API. See the Data Exchange Roadmap for available connectors. |
| User or API-Driven | Create exchanges manually through the user interface or automate creation using GraphQL mutations for scalable, repeatable workflows. |
Business Value
Exchanges solve the common challenge of collaboration across disciplines without sharing complete, heavy model files.
As an example, a structural engineering team receives an exchange containing only structural elements (beams, columns, load-bearing walls) from a complex Revit architectural model. This targeted subset enables efficient structural analysis while:
- Reducing file transfer time and storage requirements
- Maintaining data security by excluding sensitive information
- Minimizing coordination errors through focused datasets
- Accelerating decision-making with relevant information only
Common Collaboration Problems
The Challenge: Traditional file sharing forces teams to exchange entire models, even when they only need specific information.
The Problems:
- Large file sizes slow down collaboration
- Teams get overwhelmed with irrelevant data
- Security concerns sharing complete models
- Version control becomes complex
- Different software platforms struggle with compatibility
The Exchange Solution: Share exactly the data you need—nothing more, nothing less.
GraphQL Mutations
In GraphQL, a mutation is an operation used to modify data on the server. Unlike queries that read data, mutations create, update, or delete resources. In the Autodesk Data Exchange system to automate the creation of an exchange, you can use the mutation operation.
Note
The GraphQL mutation APIs create exchanges only from cloud-based source files (files stored in Forma Data Management). Exchanges from other sources are created through their respective connectors or SDKs.
The Role of createExchange
The createExchange mutation is your primary tool for generating exchanges. At a high level, it works like this:
- You specify the source: Which model or view to extract data from
- You define the target: Where to save the new exchange and what to name it
- You set any filters: What specific elements or data to include
- The system processes: Creates the exchange according to your specifications
- You receive confirmation: Get back the exchange details and status
Example
mutation {
createExchange(input: {
viewName: "Structural View"
source: { fileId: "your-revit-model-id" }
target: { name: "Structural Exchange", folderId: "target-folder-id" }
}) {
exchange {
id
name
}
}
}
This tells the system: “Create an exchange from the ‘Structural View’ in my Revit model, name it ‘Structural Exchange’, and save it to my specified folder.”
Real-World Examples
| Scenario | Exchange Solution |
|---|---|
| Structural Engineering | An architect needs to share only the structural elements (beams, columns, foundations) with a structural engineer. Instead of sending the entire 500MB Revit model, they create a lightweight exchange containing just structural components. |
| MEP Coordination | A mechanical engineer shares HVAC equipment and ductwork with a fabrication shop. The exchange excludes architectural elements, focusing only on components that need to be manufactured. |
| Facade Design | A design team shares only exterior walls, windows, and doors with a facade consultant. The consultant gets exactly what they need for their specialized review. |
| Cost Estimation | A quantity surveyor receives room data, dimensions, and material properties in a lightweight exchange for accurate cost calculations—no need to open the full architectural model. |
| Cross-Product Workflows | Teams using different software (Revit + Tekla, or Rhino + Inventor) share compatible data through standardized exchange formats. |
Creating Exchanges
Complete the setup steps in Before You Begin to prepare your environment and credentials, then choose the exchange creation method that best fits your workflow:
| Tutorial | Description |
|---|---|
| 3D View Based Exchange | Create exchanges from published views |
| AEC Data Model Exchange | Filter Revit elements by category |
| IFC Based Exchange | Work with IFC classes and Global IDs |