The architecture, engineering, and construction (AEC) industry has long relied on files to store and share information, but project success ultimately depends on how teams access and use the data within those files. In practice, much of this valuable data remains locked away in monolithic files like RVT and DWG, making it challenging to automate processes, analyze models, or enable cross-platform workflows.
The AEC Data Model changes this paradigm by enabling direct access to granular, structured data in the cloud, laying out the foundation for automation, intelligent analytics, AI-assisted design, and streamlined decision-making across the project lifecycle.
Instead of exporting data or building custom integrations for each project, teams can now access trusted, well-structured, and connected data through APIs. This shift unlocks new possibilities; no longer do workflows begin with tedious exports or rely on outdated file copies. Now, it’s possible to simply query the AEC Data Model for exactly the information needed, instantly and reliably.
With the AEC Data Model API, users can interact directly with the granular data of Revit 2024+ models hosted in Autodesk Forma (formerly Autodesk Construction Cloud). Core features include the ability to:
These functions open the door to a range of benefits. For example, teams can automate quality checks by instantly reviewing models for missing parameters, inconsistencies, or coordination issues. Real-time takeoffs and reporting become possible by accessing up-to-date quantities and estimates directly from the source data. Additionally, the API supports the creation of lightweight web applications that allow users—even those without design software—to explore and compare model data, democratizing BIM access across disciplines.
As projects have become more complex, the need to manage information that lives outside the primary model has grown. Cost data, supplier details, logistics information, and operational data are all essential, but forcing these into authoring tools can make models unwieldy and workflows fragile.
Coordinated releases in the upcoming weeks across Revit, Model Coordination in Forma, Forma Data Management (formerly Autodesk Docs), and the AEC Data Model APIs address this challenge by supporting Extended Properties.
Now, teams can author critical data like installation batch numbers or fabrication IDs in Model Coordination (coming soon) or via the AEC Data Model API. These properties are stored as datasets in Forma Data Management and can be linked directly to a model in Revit. Users can then view and use these properties in schedules and reports, creating a seamless connection between design data and downstream systems such as fabrication, cost estimation, ERP, or PLM software, all without changing their primary tools or disrupting established workflows.
So, what does this mean for project stakeholders? Autodesk uses the same APIs to build new functionality in our products. The Extended Properties feature will use the Extensibility API to create new ways to work as you can see in the video below. This new workflow allows design teams to allow non-model authoring stakeholders the ability to contribute to non-model content, like parameter values.
Imagine you’re an architect working with a door hardware consultant. Now, the consultant can add critical information to the project documentation – door hardware set data and fire ratings in this example – without ever opening the Revit model. Now, project information can be added through a simple web interface and still be tagged or scheduled in traditional project workflows. This new feature will extend who can contribute to the models and project documentation without requiring every team member to be a Revit expert.
Geometry is the backbone of design, coordination, and downstream AEC processes. The AEC Data Model API, combined with the Data Interoperability SDK (currently in pubic beta), enables direct access to structured geometry data. Developers and advanced users can:
With these capabilities, workflows such as spatial validation, automated coordination checks, and geometry extraction for fabrication have become much more efficient. Teams can conduct real-time analyses, generate room data, or extract component geometry without ever having to open Revit or export files.
To support users as they expand their use of the API, Autodesk has introduced a transparent, scalable usage model. API activities are organized into five clear categories:
The vast majority of activities, including administration, importing data, and moving data between Autodesk cloud products, are free. Currently, “Data Out” (when exporting data to external platforms) and “Transformation” incur a cost, meaning users pay only when deriving additional value beyond Autodesk solutions.
API usage is included in qualifying product subscriptions, with allowances varying by product. As an example, AEC Collection: 50 MB/month, or Navisworks Manage: 25 MB/month. There is also a free tier for developers looking to explore solutions. More information on rates and allowances can be found on the Autodesk Platform Services blog.
APIs don’t provide access to just data; they let you target the data you need. This ability to target and curate data is an important distinction as models grow in size and complexity.
The sample Revit model, Snowdon Towers, has a file size of 90MB. Instead of exporting the entire model, you can use APIs to retrieve specific, targeted, and relevant data. For example:
This shift from full model exports to targeted, granular data dramatically reduces the amount of information being transferred and processed.
The AEC Data Model API signals a fundamental shift from file-driven to data-driven workflows. By unlocking structured data and making it accessible through reliable APIs, teams gain the ability to save time, boost productivity, and automate routine tasks. The API’s transparent pricing and included usage thresholds help keep routine workflows cost-effective while encouraging richer, more connected data. Ultimately, this approach puts control in users’ hands, opening new opportunities for innovation and collaboration throughout the project lifecycle.
Join the AEC Data Model Public Beta to explore advanced in-memory geometry capabilities via Data Interoperability SDK. Additionally, explore beta capabilities like generating IFC from the AEC Data Model.
To stay up to date:
