Autodesk Forge is our collection of Application Program Interfaces (APIs) that we use to develop our own web services. As part of our Forge efforts, we share those APIs (including documentation and code samples) with customers and 3rd party developers (the Forge community) that want to leverage years' worth of legacy and current data associated with projects.
Forge is defined by 7 groups of APIs:
- Design Automation API
- Reality Capture API
- Data Management API
- Model Derivative API
- Webhooks API
With regard to the last one, Webhooks, the protocol that servers and browsers use to communicate is HTTP (Hypertext Transfer Protocol). A WebHook is an HTTP callback. In terms of web services, a WebHook manifests itself when an HTTP POST occurs when something happens; or a simple event-notification via HTTP POST. In other words, a web application implementing WebHooks will POST messages to a URL (Uniform Resource Locator) when certain things happen.
At Forge DevCon in Las Vegas that was part of Autodesk University last November, the Forge Team announced that WebHooks had been added to the Data Management portion of Forge. Since the time, the WebHook APIs have graduated to production.
Here's a video that provides a glimpse of a test harness in action:
Here's a sample application of a BIM 360 Notifier:
The code watches for various actions on files and folders in BIM 360 such as add, delete, change, etc. and lets you subscribe to being notified of the change via email, text message, and/or Slack. This sample was built in a few days. Using this code sample, most any web developer can now implement their own hooks for any and all Autodesk hubs in just a few hours.
Callbacks are alive in the lab.