21 Aug 2025

Extending AEC Data Model via GraphQL API - now in Public Beta

Attributing data outside of a model environment

The increasing complexity and scale of information required for modern AECO projects presents significant challenges. Traditional methods of consolidating data within a single BIM model, particularly in a solitary Revit file, are becoming increasingly inadequate. 

Last year, we made significant strides by unlocking element-level data from Revit, making it accessible outside the BIM model. This year, we are advancing further by delivering capabilities to extend this data directly.

With the delivery of GraphQLMutations available in public BETA, API users can now apply additional properties to specific elements of the BIM model, all without needing to copy or edit data directly into the Revit file. With this capability 

  1. More project stakeholders – not just those with expertise using Revit – can engage with model data enabling better, faster decision making 
  2. Stakeholders can append information to model element without that information residing in the model – thus reducing model bloat  
  3. Different project teams can access these custom properties outside of the BIM model using standard tools – leading to improved collaboration and streamlined project delivery.

 

This robust capability for AECO professionals will enable substantial enhancements to model data management processes, supporting increasingly data-driven digital project delivery requirements. 

The following video illustrates AEC Data Model Extensibility in action. A BIM model consists of multiple door types – each of which have a different cost and are manufactured by different suppliers. By using the mutations queries, a GraphQL user  

  1. Creates custom property definitions – Cost and Supplier 
  1. Identifies model elements - 2 different types of doors 
  1. Associates the newly created custom properties to these doors 
  1. Finds all the doors that are manufactured by a particular supplier and that costs a certain amount. 

 

In addition to the capabilities illustrated above, AEC Data Model GraphQL API now

  • Supports versioning of extended properties
  • Allows multiple clients to update extension properties – with appropriate Autodesk docs permissions
  • Returns additions/modifications/removals (DIFF) between a specific Element Group version and latest.

How to access Public BETA

To access the updated GraphQL Mutations queries, join the Extensibility Public BETA. For updated documentation on how to use the extensibility features, please visit the AEC Data Model BETA developers guide

 

More about AEC Data Model

Since its launch in 2024, the Autodesk AEC data model has democratized access to model data across project teams and been activated on over 40,000 projects, helping project stakeholders make more informed decisions based on trusted data. And the power of this information model is constantly expanding. 

The AEC data model, available to all Autodesk Docs subscribers, expands Autodesk Docs capabilities as a common data environment by extending powerful permissions, management, and collaboration capabilities beyond files to granular data. Your organization can now benefit from these new capabilities where you work today, in Docs, rather than adopting a new tool. Learn how to activate the AEC data model on your hub here.

How to get involved

Browse to the  AEC data model public roadmap to keep an eye out for more updates, new capabilities, and improved features. For questions and support needs for AEC Data Model GraphQL API, contact us via Get Help page. For general information, questions and access to generally available capabilities, please visit the AEC Data Model API page.

 

Autodesk University 2025

If you happen to be going to Autodesk University, then make sure you come to my talk where I will go into more details on this new feature:

4322: Connecting the Dots: Enhancing Collaboration and Efficiency in Projects Using the AEC Data Model API

Thursday, September 18, 10am, MCC 208B

 

----

Stay tuned for a more technical blog coming near future.

 

Related Article