The purpose of this article is to detail what information we need to be able to set up the Forge integration and to detail how this information should be passed to us in a secure way.

If you wish to have Forge enabled on both your live and beta servers, please use a different app for each. Please specify which credentials/app should be used on which server when providing the information to us.


  1. The first step of this requires having an Autodesk ID. This is the account that would be used to request support, would be connected with your subscriptions etc.

    Note: You might already have a personal Autodesk ID, but we recommend setting up a generic Autodesk ID which is linked to an email address that is regularly monitored – so someone would spot emails coming in connected with it even the current key contact were unavailable. For example a "support@" email address rather than one connected with a specific person.

  2. Your licence key must be associated with the your Autodesk ID. Please contact Autodesk support for assistance with this step if required.

  3. Set up an app for each BC server that requires Forge, using this tutorial:

    1. In step 1, follow the instructions for “If you already have an Autodesk account…”

    2. In step 2.3 under “Create App” make sure all the APIs are selected as shown in the screenshot.

    3. In step 2.4 where you enter the app name and description:

      This will be the app that is associated with your BC live or beta server. It would help if you clearly identified it so that you can quickly tell the difference between the app that you have set up for live, and the app you have set up for beta.

    4. In step 2.5: The callback URL should be set to the url of the bc server. e.g. or

    5. Make a note of the Client ID and Client Secret that are generated at the end of step 3.

    6. Upload the client ID and secret to your BC server in a file, to a location that only the uploader and the BC Admin can access, and let us know which file it is.

We will retrieve the credentials from the file on the server and store them in an offline password database with limited access. These credentials will then be applied to the server in question.