Update June 15, 2019: Design Automation for Revit (DA4R for short) is currently in public beta. I’ve created a designated page for DA4R, which I intend to update as we go along. Please refer to it for further development.
As of this writing (6/20/2018), Design Automation for Revit (DA4R) is in private beta. It’s not publicly available. But we receive inquiries quite frequently. So I’m putting together a list of available materials to learn about DA4R. I intend to update this page as more information become available.
To use DA4R, you will need to know both worlds: Revit addin as desktop application, and Forge and/or Web programming. If you are not familiar with both, you may start looking at them to be ready when DA4R is.
Below are the links to two AU/DevCon 2017 classes that talk about DA4R:
- SD125457: Design Automation: Building Web Applications with Revit Data on Forge, by Diane Christoforo
- SD124720: The New and Expanded Forge Design Automation API, by Albert Szilvasy, Andy Akenson, and Scott Reinemann
The second class is recorded and includes demos of two samples: one showing a creation of stairs (40:43) and another about updating properties (42:00). (Unfortunately, audio wasn’t recorded well for Revit portion. But you can still get the idea from images.)
The documentation for currently available Design Automation API, which is the version 2 (v2) and supports only AutoCAD, is something you may want to take a look. The v2 does not support Revit. The goal is to have the version 3 (v3) extending the support to other major Autodesk desktop products, including Revit. But you can get a big picture by looking at it:
Here is the link to Revit desktop API information if you are not familiar with Revit API:
Basically, DA4R is running Revit addin app on the remote desktop in the cloud without any user interface (UI) in a batch mode. If you already have an Revit desktop app, which you are considering to convert as automation app running on the clouds, you may start thinking about how to separate database/core portion from UI. “Without UI” means that you don’t reference to RevitAPIUI.dll and you will need to handle any input from a different source, such as a text file in JSON format instead of a dialog window. You will also need to handle errors without UI.
If you have all of above, here is a link to sign up for private beta:
Note: the product team is not accepting many beta participants at this time while they need to focus on actual implementation. We appreciate your patience while the “factory” is working hard.
You can also e-mail about private beta: