Restrictions
General restrictions for the Design Automation API
The Design Automation API imposes the following restrictions on your AppBundles, Activities and Workitems.
- Applications must be able to process jobs to completion without waiting for user input or interaction. User input must be collected prior to the job run.
- Your application is run with low privileges, and will not be able to freely interact with the Windows OS :
- Write access is typically restricted to the job’s working folder.
- Registry access is mostly restricted, writing to the registry should be avoided.
- Any sub-process will also be executed with low privileges.
- Uploaded contents are unzipped on Design Automation machines. Prefer shorter path lengths to avoid going over the 260 characters limit for Windows paths.
For network environments where access is limited, Design Automation requires access to the following addresses at a minimum:
- APS Authentication Service https://developer.api.autodesk.com/authentication/v2/token
- DAS API Root https://developer.api.autodesk.com/da/us-east/v3/*
For network environments where access is limited, the following addresses are optional for Design Automation access:
- Object Storage Service (OSS) https://developer.api.autodesk.com/oss/v2/*
- Upload AppBundle (AWS) https://dasprod-store.s3.amazonaws.com/apps/*
- Get WorkItem Report (AWS) https://dasprod-store.s3.amazonaws.com/workItem/*
Design Automation API for Inventor
The Design Automation API for Inventor imposes the following restrictions on your AppBundles, Activities and Workitems.
- No access to Inventor’s UI interfaces. Your application must only interact with the InventorServer object.
- Writing to the disk is restricted to Inventor’s current working directory.
- Some of the Inventor common addins are not supported on Design Automation. These currently include:
- Frame Generator
- Tube & Pipe
- Cable & Harness
- Mold Design
- Design Accelerator
- Export of data into native Microsoft Office formats is not supported. This includes exporting BOM data into an MS Excel file. However, export to a .csv file is supported.
In order to process the “onComplete” or “onProgress” callback behind a firewall, the following IPs need to be allowed for Inventor:
- 52.20.163.163
- 18.210.124.48
- 3.90.98.123
Design Automation API for Revit
The Design Automation API for Revit imposes the following restrictions on your AppBundles, Activities and Workitems.
- No access to Revit’s UI interfaces. Your application must be a RevitDB application only.
- Writing to the disk is restricted to Revit’s current working directory.
- There is no access to the ActiveView or ActiveDocument property for AppBundles that run on Design Automation API for Revit.
- Export to Navisworks functionality is not available.
- Autodesk Desktop Connector is not supported.
- 3.229.167.149
- 44.207.230.78
- 54.175.193.194
Design Automation API for 3ds Max
The Design Automation API for 3ds Max imposes the following restrictions on your AppBundles, Activities and Workitems.
- Writing to the disk is restricted to 3ds Max’s current working directory.
- Only 3dsmaxbatch.exe is supported as an engine, 3dsmax.exe is not supported.
- There are no GPUs on Design Automation machines. Any features requiring access to a GPU will not be supported (for example the Quicksilver Hardware renderer).
- APIs used to interact with 3ds Max’s user interface are not supported.
- ActionMan is not supported.
- Loading and saving compressed max files is not supported.
In order to process the “onComplete” or “onProgress” callback behind a firewall, the following IPs need to be allowed for 3ds Max:
- 18.213.152.234
- 54.85.240.25
- 18.208.26.46
Design Automation API for AutoCAD
In order to process the “onComplete” or “onProgress” callback behind a firewall, the following IPs need to be allowed for AutoCAD:
- 35.170.46.104
- 3.211.89.243
- 3.210.87.162
Design Automation API for Fusion
The Design Automation API for Fusion imposes the following restrictions on your AppBundles, Activities and Workitems.
- No access to Fusion’s UI interfaces.
- Writing to the disk is restricted to Fusion’s current working directory.
- You are able to create setups and operations, however you are unable to generate subtractive toolpaths that require in-process stock or generate toolpaths for the following five strategies: Rotary Pocket, Rotary Contour, Deburr, Advanced Swarf, Geodesic, 3+2 Clearing, Multi-Axis Clearing, Multi-Axis Finishing.
In order to process the “onComplete” or “onProgress” callback behind a firewall, the following IPs need to be allowed for Fusion:
- 3.211.233.210
- 98.85.136.172
- 98.85.144.85