In this class you will see how you can use the Vault software API and the View and Data API together. The View and Data API enables you to programmatically view models in 3D in a browser. The Vault software API enables you to download files from Vault software. The topics covered in this class will be from an application that uses C# Vault API calls to download files along with View and Data API REST calls to translate the files. You will see how to use the View and Data API JavaScript functions to view the translated files. Please note that prior programming knowledge with C#, REST, and JavaScript is recommended. This class is not suitable for people who do not have any programming experience.

In this session, we’ll go through the BIM 360 APIs that have been recently added and are in-pipeline for near future releases. By Autodesk University Las Vegas time frame, we hope to cover the new Model Coordination API and Cost API, a newer version of Admin API, various enhancements to Field Management API, and more. This class assumes your familiarity with BIM 360 products and basic web programming knowledge, such as HTML and REST API. Hands-on experience with Forge APIs will be a plus, but is not necessary for decision makers.

This class will guide you through the new, exciting, cloud-based API for InfraWorks 360 software. We will cover how to get started and extract data from the model, how to generate report from the extracted information, and how to integrate with other providers—all by reading InfraWorks 360 software models using the REST API. Previous programming knowledge is required (Microsoft C# and Microsoft .NET), and knowledge of REST and the JavaScript API is recommended.

Traditionally, firms have developed and deployed Revit Add-ins using C# to implement Automation, Integration, & Customizations and custom capabilities in Revit. Autodesk now offers the  Automation, Integration, & Customization API, part of the Autodesk Platform Service (APS), which provides access to the Automation, Integration, & Customization capabilities of Autodesk’s core products, including the Revit API. This session will assist developers in transitioning from the Revit API to the Automation, Integration, & Customization API. The Automation, Integration, & Customization API introduces a new workflow that allows developers to access the full Revit DB API without needing a Revit desktop installation. This enables seamless creation, extraction, and modification of Revit data. This workflow facilitates the creation of custom Revit families, data extraction, and more, without the need to open Revit models. We outline from start to finish how to convert a Revit Add-in to Design Automation, Integration, & Customization. This includes using Postman, managing References, Access Tokens, AppBundles, publishing, and running WorkItems.

In this class, we introduce you to the BIM 360 Glue API. The Glue API is composed of 2 parts: a web services API and a display component (viewer). The web services API is REST-based. It allows you to access BIM 360 project data in the cloud, such as users, models, and actions. The display component (or viewer API) can be embedded in your application. It provides additional control to its user interface and allows you to customize the viewing experience. Using the Glue API, you can, for example, automate updating projects and models from external applications. BIM 360 Glue keeps track of user's actions as data in addition to traditional model-centric information, which can be used for progress tracking, health monitoring of projects, and so on. As BIM 360 Glue is totally cloud-based, you can connect your own web services applications with the Glue projects. We also show you examples of use cases and demonstrate what you can do using the Glue API. This class assumes you have a basic understanding of web programming, such as web services. Working knowledge of the REST API is helpful for understanding the discussion.

In this class, we will introduce you to BIM 360 Docs software’s API. BIM 360 Docs software is a cloud-based document management system tailored specifically for construction projects. As the document at the center of BIM 360 family products, BIM 360 Docs software promises to play an important role for unified development of the BIM 360 mobile and web platform. BIM 360 Docs software provides an API as a part of the Forge Platform Data Management API. Using the Forge Platform API, you can access documents stored in BIM 360 Docs software, display models using the Viewing API, and search data in the model. Using the API, for example, you can automate updating models from external applications, make a report to keep track of a team’s progress, and connect your own web services applications with BIM 360 Docs projects. We will show you how to get started with the BIM 360 Docs API, share examples of use cases, and demonstrate what you can do using the BIM 360 Docs API. This session features BIM 360 Docs and Forge. AIA Approved

Its not just AutoCAD anymore - the Design Automation API now includes Revit and Inventor. This class presents an introduction to newly expanded Forge Design Automation API. Members of the Revit, AutoCAD and Inventor Design Automation teams will discuss the general API architecture, specific implementation details and examples for automating the three products separately and in concert. (Joint AU/Forge DevCon class).

Come and discover the BIM 360 Glue software API. This API (application programming interface) is composed of 2 parts: the Web Services API and the display component. The Web Services API is REST-based, and it enables you to access your BIM 360 Glue software data, such as users, models, and actions. You can imbed the display component, or Viewer API, in your application. Using the BIM 360 Glue software API, you can, for example, automate the updating of projects and models from external applications. BIM 360 Glue software keeps track of a user's actions as data in additional to traditional model-centric information. You can also use such information to make a report that will keep track of a team's progress. Of course, BIM 360 Glue software is totally cloud based, so you can connect your own web services applications with the BIM 360 Glue software projects. We will also use examples of use cases to demonstrate what you can do with the BIM 360 Glue software API.

This is the #1 geek-out event for Autodesk, Inc., API programmers. Our panel of hardcore ObjectARX API and AutoCAD .NET API experts from the AutoCAD Development Team is ready to answer your programming questions. If you're writing plug-ins for AutoCAD software, this is the perfect forum to get to know the people who create the APIs you work with, as well as your fellow programmers who use those APIs. Come and ask questions, add your expertise to the discussion, or just listen and learn.

Revit software customization via the Revit API has continued to grow in popularity over the last several years. Because of the complexity of Revit software and the extensiveness of the Revit API, new Revit software add-in developers often run into similar problems and repeatedly ask questions of the customer support or on social media and forums. This course collects many of the most-frequently asked questions and most-likely encountered problems into a single presentation. In this lecture you will see common solutions to typical problems, discover often repeated Dos and Don’ts, and learn recommended approaches to developing and structuring Revit software add-ins. For each topic we will review the mistakes or roadblocks developers typically stumble upon and show the recommended solution while illustrating the answers with useful examples you can borrow from or modify. This course assumes the working knowledge of Microsoft .NET programming and experience with the Revit software API.

The AEC Data Model API enables access to data that is more detailed than anticipated, significantly enhancing possibilities for data verification and data management. In our session, we will present several case studies on data verification using the AEC Data Model APIwith Excel and Power BI, as well as data management using the AEC Data Model API and the Revit API. Additionally, data verification is also possible with the Data Exchange API,and we will briefly explain the differences between the Data Exchange API and the AEC Data Model API.

Are you interested in learning BIM 360 and Forge, but not sure where to start? Are you feeling confused about how Forge APIs work together to give you access to your BIM data? If so, this class is for you. In this session, we'll look at the Forge API from the view of BIM 360 products and provide you with the foundational knowledge for you to implement powerful applications and workflows using these APIs.

In this class, we will present the current status of the APIs for Construction Cloud software, discussing the APIs that have recently been added and those that we expect to release in near future.

Attend this class to learn how to share your design proposals among your stakeholders using cloud-based API for InfraWorks 360 software. We will cover how to get started, extract data from the model, and share the data on other web- and cloud-based apps—all by reading models, proposals, and features using the REST API. Prior programming knowledge is required (C# and Microsoft .NET) and understanding of REST and the JavaScript API is recommended.

The Model Derivative API is not just meant for translating files to a viewing file format (the 'SVF' file ) and loading the model for viewing. In this class, we will provide you with deeper understanding of the Model Derivative API, it's feature set and capabilities. We will cover the range of file formats that are available for translation; how to extract metadata from a model; and how geometry can be extracted from model data for developing a variety of custom Forge applications. This will be followed by demonstrating a use case developed by one of our Forge customers. The class will show side by side samples of C# and Node.js.

Gain a better understanding of how Inventor software’s iLogic functionality works, and learn about other tools that can help make writing iLogic rules much easier. In addition, learn how you can use Inventor software’s API and the .NET Framework to create much more powerful rules. Finally, learn what capabilities Inventor software add-ins provide so you can make a logical choice about which provides the best fit for you. This session features Inventor Professional and Inventor Professional.

This class will demonstrate how to explore the Dynamo API through Visual Studio and C#. Learn how to navigate the core libraries, understanding the difference between methods and properties within classes, and how to build simple commands. Much like the Revit API, understanding the application of the Dynamo API can open up further opportunities for future development. Finally, learn about some of the potential use cases of its application and see some real world examples of this.

In this session, we'll present the latest status of Autodesk Construction Cloud APIs. We'll discuss the APIs that have recently been added, and we'll explore what we expect to release in the near future.

The Forge Design Automation API is a cloud-based service that enables the automation capabilities of AutoCAD software, Inventor software, Revit software, and 3ds Max software. This presentation will explain and demonstrate two new features that increase the service’s capabilities. First, the preview feature of Open Network Access breaks down a longstanding barrier wherein the Design Automation API disallows network access during the running of a job. Letting customers add in access networks through HTTP(S) calls will solve some problems of workflows currently running in the Design Automation API, and will help extend the scope of work processes that the Design Automation API can support. WebSocket endpoints is another new offering that points back to client devices (desktop, mobile, or laptop), sending progress and completion responses so the applications don't need to make repeated Get requests—plus no callback for onComplete argument is needed to find the status of a job. We will also introduce and demo other small but peppy features that the Design Automation API has supported since last year.