Expanding regional offerings in UK, Germany, Japan, India, and Canada

What's new in Autodesk regional offerings?

On June 30, Autodesk announced the availability of five (5) additional regions as a primary storage location for your project data for certain Autodesk Construction Cloud (ACC) products: the United Kingdom, Germany, Japan, Canada, and India. For example, as a primary account admin , you can create an ACC hub in any of the regions above for your team in manage.autodesk.com and activate an Autodesk BIM Collaborate account. The newly created ACC account will use the specified region as the primary storage location for your Autodesk BIM Collaborate project data.  

The benefits of the expansion of primary storage regions include:  

• Greater choice and control over the primary storage location of your project data  

• Optimized latency if using these services in the region closer to you  

In this regional expansion, the following products are available: 

• Autodesk Docs 

• Autodesk BIM Collaborate 

• Autodesk BIM Collaborate Pro (includes Revit Cloud Worksharing and Collaboration for Civil 3D)    

For more information about this offering, a more detailed list of available services and tools within ACC products, please see  here. 

What does this mean for your apps? 

Accompanying this expansion, selected Autodesk Platform Services APIs are available for those regions as well:  

• Data Management API*1   

• Model Derivative API   

• Webhooks API   

• Viewer SDK   

• Autodesk Construction Cloud APIs*2  

In short, the official values used to indicate for U.K./Germany/Japan/Canada/India will be GBR/DEU/JPN/CAN/IND respectively (following ISO 3166 alpha-3 country code as standard moving forward).  

Some apps may need to be updated to take advantage of this new region’s expansion.  The update is minimum, yet a few points to note/reminder regarding regional support:  

• ACC APIs and automatic region routing -- All ACC APIs support automatic region routing. The endpoint you use for US works for all regions by default.  This will make the coding for future regional expansion easy. The older admin API, that has separate endpoints for the EU region, will remain functional for backward compatibility.  

• Region in Request – Some APIs require a region field to be provided. This applies to  Data Management/Model Derivative/Webhooks API; and to ACC APIs that take an optional region header.   

• Region in Response – Response body from the API call may include the same region code. *1   

• Viewer – Viewer version 7.109.1 and above is required to support automatic region routing for models hosted in the new 5 regions, this includes models in Autodesk Docs and OSS. Set the feature flag DS_ENDPOINTS before viewer initialization to enable the routing. Check v7.109.1 at change history for details. 

*1) Reminder: As of June 30, 2025, region code for Australia is either “APAC” or “AUS” while transitioning to “AUS”. If your code requires information, you need to check against both values in your code until the transition is completed, which is scheduled for July 31, 2025. See this blog for more details.  

*2) ACC APIs are available for supported ACC products and features only. For example, Autodesk Takeoff and Autodesk Build specific API will not be available at this point.          

Where to get support? 

If you have any questions regarding API related to this regional expansion, please contact support.