Fusion API and Scripts
Got a new add-in to share? Need something specialized to be scripted? Ask questions or share what you’ve discovered with the community.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

New Functionality and JavaScript Moves to Maintenance Mode

Message 1 of 6
994 Views, 5 Replies

New Functionality and JavaScript Moves to Maintenance Mode

I don't know if you read the "What's New" page in the June 2017 update for Fusion or not but there were a few nice additions but also one very big announcement.  I suspect more people might see the information posted here so I'm going to repeat the information here and will start with the announcement first.



The Fusion 360 product team constantly monitors analytics data to get information about how Fusion 360 is being used to help make decisions about where to focus resources for future development. This information is also useful in identifying areas of Fusion 360 that have very little usage. In some cases these areas are retired in order to focus resources on the portions of the product that will benefit the most people. One area that has been identified as have very little usage is the JavaScript API interface. With the upcoming July 24th update, Fusion 360 will be moving the JavaScript API interface into maintenance mode.


"Maintenance mode" in this case means that documentation for the JavaScript API will be removed from the online help and the capability to create new JavaScript scripts and add-ins will be removed from the Scripts and Add-Ins dialog. However, the actual JavaScript interface will continue to be delivered, but without any new enhancements, to allow any existing JavaScript scripts and add-ins to continue to run and be used and they will still appear in the Scripts and Add-Ins dialog so they can be run.


This was a difficult decision to make and we understand it is not good news if you've been using the JavaScript API. It takes continued resources from the Fusion 360 team to create, test, document, and support any API and based on usage numbers there are very few users using JavaScript to program Fusion 360. So, the decision was made to move it into maintenance mode and concentrate our efforts on the Python and C++ interfaces.


As mentioned above, existing programs will continue to run as they do today. It's possible the JavaScript API will be retired and completely removed from Fusion 360 at some point in the future but that has not yet been determined. You're encouraged to re-write your existing programs in Python or C++. Please feel free to contact us at with your concerns and comments.



  • User Specified Program Path - You can now specify the location where Fusion will look for existing scripts and add-ins and where new scripts and add-ins will be created. You do this using a new setting in the Preferences dialog, as shown below. The default path was deep and in a system folder. With this you can choose the location of your programs. This path is not saved as part of your cloud preferences but is a local preference. This allows you to have a different path on different computers.

    A big benefit of being able to choose your script and add-in location is that this can be a folder that is synced to the cloud using any of the available file syncing services.


  • Change in Adding Script or Add-In - A small change has been made to how you add a script or add-in to the list of known scripts and add-ins. The "Scripts and Add-Ins" dialog allows you to select a script or add-in anywhere on your computer and Fusion 360 will remember it after that. You do that by using the green "+" button on the "Scripts and Add-In" dialog, as shown below. This also helps to resolve a security issue on Mac where selecting just the file didn't provide access to the other files in the folder. Selecting a folder provides access to its entire contents.


    Clicking the green plus will display a browse dialog where you can browse to and select the script or add-in. The change is that previously you had to pick the file that represented the script or add-in. This tended to be confusing because these files will have different file extensions depending on which language the script or add-in was written and it was possible that there could be multiple code files that the main file depended on. The change is that you no longer select the file but now choose the folder that contains all of the files of the script or add-in.


  • Change to ModelParameter.createdBy property - The createdBy property of the ModelParameter object was changed in the previous update so that it will return the object that caused the parameter to be created. There are cases where the creating object isn't currently supported by the API so the createdBy property doesn't have anything to return. In the last update, when this occurs it results in an exception. This has been changed in this update to that the property returns null instead.

  • Clearing a List - A problem was reported on the forum quite a while ago regarding being able to empty the list associated with a DropDownCommandInput. This has been resolved in this update with the addition of the clear method to the ListItems object.

  • Additional Feature Support - Support for copying or cutting and pasting a body is now supported through the API. Basic query support it now also available for the offset face feature (which is created in the UI using the "Press Pull" command).

  • External References - Additional functionality related to external references has been added to the API.

The full list of changes can be found on the What’s New page of the Fusion API help.

Brian Ekins
Inventor and Fusion 360 API Expert
Mod the Machine blog
Message 2 of 6
in reply to: ekinsb

I would say some of the cam guys wont like this

Win10 pro | 16 GB ram | 4 GB graphics Quadro K2200 | Intel(R) 8Xeon(R) CPU E5-1620 v3 @ 3.50GHz 3.50 GHz

Daniel Lyall
The Big Boss
Mach3 User
My Websight, Daniels Wheelchair Customisations.
Facebook | Twitter | LinkedIn

Message 3 of 6
in reply to: ekinsb

What a pity!


Any plan to support Fusion360 rest apis like Forge?

Message 4 of 6
in reply to: mycad2016D8W4P

It doesn't make sense to support a REST API for the current Fusion 360.  A REST API is used to communicate with a web service and Fusion 360 is a local application.  Where it would make sense in the future is if we support accessing Fusion on the cloud like the current Design Automation API for AutoCAD that is part of Forge.  That's something we talk about but is not something we're actively working on at the moment.

Brian Ekins
Inventor and Fusion 360 API Expert
Mod the Machine blog
Message 5 of 6
in reply to: ekinsb

I'd say the big pro of offering a REST interface would be decoupling the language specific support burden from Autodesk.

Message 6 of 6
in reply to: ekinsb

Thanks Brian. I did mean the plan about putting Fusion360 on server.

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Autodesk DevCon in Munich May 28-29th

Autodesk Design & Make Report