What is Autodesk Data Exchange .NET SDK?
Autodesk Data Exchange .NET SDK is a developer toolkit for building custom interoperability workflows that share your design data across Autodesk products and third-party applications. It gives .NET developers APIs to create, read, update, and synchronize Data Exchanges, work with structured element data and geometry, and connect those workflows to their own applications and services.
For teams that are new to Autodesk Data Exchange, the core idea is simple: Autodesk Data Exchanges facilitate applications to share curated, granular design data instead of moving an entire design model every time. The SDK gives developers programmatic control over that exchange workflow so they can build integrations around the data their users actually need.
What can you build with the Data Exchange SDK?
The Data Exchange SDK is designed for developers who need more flexibility than an out-of-the-box connector can provide. You can use it to build custom connectors, automate model-data workflows, enrich exchange data, and move information into downstream systems or industry formats.
-
Custom connectors. Create integrations between Autodesk workflows and third-party applications, internal tools, analysis systems, or data pipelines.
-
Structured data workflows. Read and update exchange elements, work with element classifications and type information, and attach parameters that downstream applications can interpret consistently.
-
Geometry workflows. Work with exchange geometry through the SDK conversion and geometry APIs, including workflows that use mesh and boundary-representation (BRep) data.
-
Industry-format workflows. Download complete exchanges in formats such as USD, OBJ, STEP, and IFC when your workflow needs a file-based handoff.
-
Incremental processing. Retrieve the latest exchange changes so applications can react to updates without treating every interaction as a brand-new workflow.
Who should take a look at the Data Exchange SDK?
The SDK is a good fit for software vendors, systems integrators, enterprise development teams, and connector developers that need to move structured Autodesk model data into another application or workflow. It is also relevant to teams building automation around model data, geometry processing, data enrichment, validation, or downstream analytics.
How do you get started?
For new developers, the best starting point is a small end-to-end workflow: authenticate, open or create an exchange, inspect a few elements, make one controlled update, synchronize it, and then build outward from that working pattern.
-
SDK usage samples
What should existing beta developers know before upgrading?
If you already built against an older beta release, review the GA documentation before recompiling. Several public APIs changed during the beta program, including element interfaces, validation hooks, geometry-conversion paths, and package dependencies. The final GA changelog should clearly identify any additional changes between the last beta and the GA build.