Autodesk BIM 360

Autodesk BIM 360 is a cloud-based construction management platform, part of Autodesk Platform Services (APS). This connector manages construction project, user, company, and industry-role directory data through the BIM 360 Account Admin (HQ) and Construction Admin APIs, letting you read and write account and project administration records.

Power end-to-end data operations for your Autodesk BIM 360 API with Nexla. Our bi-directional Autodesk BIM 360 connector is purpose-built for Autodesk BIM 360, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Autodesk BIM 360 or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Autodesk BIM 360 workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating an Autodesk BIM 360 credential, you need to register an app on the Autodesk Platform Services (APS) developer portal to obtain a Client ID and Client Secret, provision that app for API access in BIM 360 Account Admin, and locate your BIM 360 Account ID. This connector authenticates using APS OAuth 2.0 client-credentials (2-legged) authentication, where the app communicates directly with APS for access tokens without requiring an interactive user login.

To obtain your Autodesk BIM 360 credentials, follow these steps:

1. Sign in to the Autodesk Platform Services developer portal with your Autodesk account.

2. Navigate to the Applications page from your account menu, then click Create application.

3. Enter a name for your app (e.g., "Nexla Integration") and select the Server-to-Server App type, which supports the client-credentials (2-legged) grant used by this connector.

4. After the app is created, open its detail page and copy the Client ID and Client Secret. Store the Client Secret securely, as it grants access to your Autodesk data.

5. Provision the app for BIM 360 API access. Sign in to BIM 360 Account Admin, click Settings, and select the Custom Integrations tab.

6. On the Add Custom Integration screen, select the BIM 360 products you want to grant API access to and click Next, then select I'm the developer, enter your Client ID and the app name, and complete the provisioning.

7. Locate your BIM 360 Account ID in Account Admin > Account Settings. Use the account ID without the b. prefix, as the HQ API expects the raw account identifier.

For complete information about app registration, provisioning, and authentication, see the Autodesk Platform Services documentation and the Create an App tutorial.

Authenticate

Credentials required

APS OAuth 2.0 client-credentials (2-legged). Create an app on the APS portal, add as a service under Account Admin > Services with Client ID/Secret + account ID.

Field	Required	Secret	Description
Client ID	Yes	No	The Client ID of your Autodesk Platform Services (APS) app, from the APS developer portal app page.
Client Secret	Yes	Yes	The Client Secret of your Autodesk Platform Services (APS) app.
BIM 360 Account ID	Yes	No	The BIM 360 hub/account ID (without the 'b.' prefix) found in Account Admin > Account Settings; scopes every HQ API request.

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Enter the Client ID of your APS app in the Client ID field.

4. Enter the Client Secret of your APS app in the Client Secret field. This value is sensitive and should be kept confidential.

5. Enter your BIM 360 Account ID in the BIM 360 Account ID field, using the account ID without the b. prefix. This value scopes every HQ API request to your account.

   If your Client Secret is compromised, regenerate it from your app page on the Autodesk Platform Services developer portal and update the credential in Nexla.

6. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Autodesk BIM 360 connector tile, then select the credential that will be used to connect to Autodesk BIM 360, and click Next; or, create a new Autodesk BIM 360 credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Autodesk BIM 360 endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

[Rest API] Projects

Retrieves the list of BIM 360 projects in the account, including project id, name, status, and project type.

• This endpoint fetches projects scoped to the account ID in your credential. Nexla automatically handles pagination to retrieve all available records.

[Rest API] Get Project

Retrieves details of a single BIM 360 project, including services activated and project admins.

• Enter the Project ID of the project to retrieve. This is the BIM 360 project ID returned by the Projects endpoint, without the b. prefix.

[Rest API] Users

Retrieves the list of users in the BIM 360 account directory, including user id, email, name, status, and company name.

• This endpoint fetches account directory users scoped to the account ID in your credential. Nexla automatically handles pagination to retrieve all available records.

[Rest API] Get User

Retrieves details of a single user in the BIM 360 account directory.

• Enter the User ID of the user to retrieve. This is the BIM 360 account/project user ID returned by the Users endpoint.

[Rest API] Companies

Retrieves the list of partner/member companies in the BIM 360 account directory, including company id, name, and trade.

• This endpoint fetches companies scoped to the account ID in your credential. Nexla automatically handles pagination to retrieve all available records.

[Rest API] Get Company

Retrieves details of a single partner/member company in the account directory.

• Provide the company identifier for the company whose details you want to retrieve, as returned by the Companies endpoint.

[Rest API] Project Users

Retrieves the list of users assigned to a BIM 360 / ACC project, including their roles, companies, and access levels.

• Provide the Project ID of the project whose assigned users you want to retrieve. Nexla automatically handles pagination to retrieve all available records.

[Rest API] Get Project User

Retrieves details of a single user's assignment (roles, company, products) on a BIM 360 / ACC project.

• Provide the Project ID and the User ID that identify the specific project assignment you want to retrieve.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Autodesk BIM 360 data sources can also be manually configured to ingest data from any valid BIM 360 or APS API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Autodesk BIM 360 data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination

Click the + icon on the Nexset that will be sent to the Autodesk BIM 360 destination, and select the Send to Destination option from the menu. Select the Autodesk BIM 360 connector from the list of available destination connectors, then select the credential that will be used to connect to Autodesk BIM 360, and click Next; or, create a new Autodesk BIM 360 credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Autodesk BIM 360 endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

[Rest API] Create Project

Creates a new BIM 360 project in the account.

• Each record from your Nexset is sent as a JSON request body to create a new project. The record structure must match the fields expected by the BIM 360 Construction Admin API for project creation.

[Rest API] Create User

Adds a new user to the BIM 360 account directory and optionally assigns them to projects.

• Each record from your Nexset is sent as a JSON request body to add a new account directory user. The record structure must match the fields expected by the BIM 360 HQ API for user creation.

[Rest API] Update User

Updates an existing account user's status, company, or job title.

• Each record is sent as a JSON request body to update an existing account user. Include the user identifier so the correct directory record is updated.

[Rest API] Create Company

Creates a new partner/member company in the account directory.

• Each record from your Nexset is sent as a JSON request body to create a new company. The record structure must match the fields expected by the BIM 360 HQ API for company creation.

[Rest API] Update Company

Updates an existing partner/member company's name, trade, or address.

• Each record is sent as a JSON request body to update an existing company. Include the company identifier so the correct directory record is updated.

[Rest API] Add Project User

Assigns an account user to a BIM 360 project with specified industry roles and products access.

• Each record is sent as a JSON request body to assign a user to a project. Include the project identifier along with the roles and products access to grant.

[Rest API] Update Project User

Updates a project user's industry roles, company, or products access.

• Each record is sent as a JSON request body to update a project user assignment. Include the project and user identifiers so the correct assignment is updated.

Manual configuration

Autodesk BIM 360 destinations can also be manually configured to send data to any valid BIM 360 or APS API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

Autodesk BIM 360 APIs expect JSON format for write operations. For update operations, include the ID of the object to be updated at the end of the request URL.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Autodesk BIM 360 endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the Autodesk BIM 360 endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.