Overview
What is BIM 360 Docs: BIM 360 Docs is Autodesk's cloud document management module for built-world teams to create, mark up, and share 2D drawings, 3D models, plans, and specs, with version control, issue tracking, transmittals, and permission-controlled folders. Autodesk has since rebranded BIM 360 Docs to Autodesk Docs and, on March 24, 2026, to Forma Data Management, but the BIM 360 API remains operationally active for the many firms still running projects on BIM 360. Those endpoints only work with BIM 360 projects, so teams that have migrated to Autodesk Construction Cloud should use the ACC integration instead.
How to integrate BIM 360 Docs with Datagrid
The BIM 360 Docs Datagrid integration links your BIM 360 hub to Datagrid via Autodesk Platform Services (APS), enabling agents to process selected project data without manual export steps. The Data Management API exposes the full hierarchy of hubs, projects, folders, items, and versions; Datagrid reads folders, files, versions, issues, RFIs, and some project administration objects, and file and item sync runs bidirectionally so agents both read project files and write updates back. APS webhook events such as dm.version.added trigger agents the moment something changes in a project folder. Follow this setup order: connect your BIM 360 hub, authorize Autodesk access, then configure the data sync.
Connect your BIM 360 hub
Connect the BIM 360 hub and project folders Datagrid should index.
Open your Datagrid workspace and go to Settings > Integrations > Add New.
Search for BIM360 Docs and select it.
Click Connect to start the OAuth authorization flow.
Sign in with your Autodesk account credentials.
Grant the requested permissions: read/write access to project data, documents, and account information.
Select the BIM 360 hub and project(s) you want to connect.
Confirm the connection; Datagrid begins indexing your project data.
A completed connection records the selected BIM 360 hub, projects, folders, permission mode, and connection status.
datagrid_bim360_connection:
integration: BIM360 Docs
hub: selected_hub
projects:
- selected_project
folders:
- selected_folder
permission_mode: read_write
status: connectedAuthorize Autodesk access
Datagrid uses OAuth 2.0 through Autodesk Platform Services. Most document management endpoints require a three-legged OAuth token, so a user must authorize the connection. Two-legged (app-only) tokens work only for specific Account Admin endpoints. Datagrid handles the OAuth flow automatically during setup. All calls require explicit token scopes; data:read is the minimum for document access.
Use this OAuth scope configuration as the baseline for document access and write-back.
autodesk_oauth:
flow: three-legged
minimum_document_scope: data:read
write_back_scope: data:write
authorization_owner: BIM 360 project userA BIM 360 account administrator must provision third-party apps under Account Admin > SETTINGS > Custom Integrations. Without this step, the Data Management API will not list BIM 360 Docs hubs for the authorizing user. The Getting Started tutorial covers this account provisioning step.
Configure data sync
Configure the BIM 360 objects Datagrid should read, write, and monitor for agent execution.
Folders: Read and write, Data Management API v2
Files and items: Bidirectional, Data Management API v2
File versions: Read and write, Data Management API v2
Issues: Read and write, BIM 360 Issues API v2
RFIs: Read, BIM 360 APIs
Project admin objects: Read, BIM 360 APIs
BIM 360 Docs supplies drawings, specs, file versions, issues, and RFIs. Submittal tracking requires the BIM 360 Build integration or another connected submittal system.
Webhook events drive sync when project files change. The Webhooks API fires version, folder, and lineage events, and agents process changes as they land.
A Datagrid sync configuration can record the selected APS hierarchy as the processing boundary.
bim360_docs_sync:
hub: selected_hub
projects: selected_projects
folders: selected_folders
objects:
- folders
- files
- file_versions
- issues
- rfis
trigger_events:
- dm.version.addedDatagrid needs the hierarchy exposed by the Data Management API to connect folders, items, and versions.
{
"hub": "selected_hub",
"project": "selected_project",
"folder": "selected_folder",
"item": "drawing_or_project_file",
"versions": [
"previous_version",
"new_version"
]
}When a new version lands in a monitored folder, the webhook trigger should clearly identify the event type. Event type: dm.version.added.
{
"eventType": "dm.version.added",
"hub": "selected_hub",
"project": "selected_project",
"folder": "selected_folder",
"item": "drawing_or_project_file",
"version": "new_version"
}Before an agent processes the event, verify that the event type and project boundary match the configured BIM 360 sync.
function verifyBim360Event(event, allowedProjects, allowedFolders) {
if (event.eventType !== "dm.version.added") return false;
if (!allowedProjects.includes(event.project)) return false;
if (!allowedFolders.includes(event.folder)) return false;
return Boolean(event.item && event.version);
}For endpoint details before expanding the folder or version scope, refer to the Data Management guide.
Why use BIM360 Docs with Datagrid
Datagrid uses BIM 360 Docs as an execution layer for drawing control and RFI review, with version monitoring tied to APS events.
Bidirectional file sync: Datagrid reads and writes folders, files, and versions through the Data Management API, so metadata updates flow back into BIM 360.
Event-driven execution: Webhook events such as
dm.version.addedtrigger agents the moment a new drawing version uploads.Automated drawing classification: Agents extract title block data, sheet numbers, disciplines, and revision levels, then tag project files without manual data entry.
RFI intelligence: Agents read RFI content, cross-reference spec documents, classify by type, and draft responses from historical RFI data.
Cross-platform routing: Agents move file data and RFIs between BIM 360 Docs and other connected built-world platforms.
Version comparison at scale: Agents compare document versions, flag changes by severity and discipline impact, and reduce the risk of teams building from superseded drawings.
What you can build with BIM360 Docs Datagrid integration
BIM360 Docs with Datagrid supports repeatable document-control outcomes from the same source of record. The workflows below show how agents execute specific tasks across active projects.
Drawing intake and classification pipeline: An agent watches a project's upload folders and processes each new drawing set. It extracts sheet and revision data, including discipline, then applies consistent metadata tags. Document control teams retrieve sheets by sheet number and revision metadata, with discipline available as a filter.
RFI analysis and response drafting: When a new RFI arrives, an agent reads it and pulls the relevant spec sections. It classifies the RFI by type and drafts a response from historical RFI data. The engineer of record reviews that draft.
Submittal cross-checking against specs: Agents cross-check submittals from BIM 360 Build or other connected submittal systems against drawings and flag discrepancies between submitted materials and specification requirements. Pair this with BIM 360 Build for submittal tracking through the full review lifecycle.
Version change detection and routing: A
dm.version.addedevent triggers an agent to compare the new drawing against the prior version. The agent flags changes by severity, identifies affected disciplines, and alerts the right leads. Teams that pull clash data via the Navisworks integration can correlate flagged changes with coordination results before building from superseded drawings.
Resources and documentation
BIM 360 API overview: Entry point for BIM 360 APIs on the APS developer portal.
Data Management guide: Explains folders, items, and versions across BIM 360 Docs projects.
Getting started tutorial: Explains how to provision custom apps in BIM 360 Account Admin.
App creation tutorial: Explains how to register an APS app and save client credentials.
Webhooks developer guide: Explains how to listen to APS events on hubs, projects, folders, and files before agents respond to project changes.
Frequently asked questions
Does the integration work with Autodesk Construction Cloud projects?
No. BIM 360 API endpoints only work with BIM 360 projects, and ACC API endpoints only work with ACC projects. If your organization has migrated to Autodesk Construction Cloud, connect those projects through the ACC integration instead.
Which authentication method does the integration use?
OAuth 2.0 through Autodesk Platform Services. A project user authorizes the connection during setup. Document access requires explicit token scopes; data:read is the minimum for document access.
Why is my BIM 360 hub missing after authorization?
A BIM 360 account administrator has not provisioned the integration yet. The Data Management API will not list BIM 360 Docs hubs until the admin adds the app under Custom Integrations in Account Admin. The authorizing user also needs access to Docs > Files with at least one visible file.
How quickly do agents react to a new file version?
The dm.version.added event fires as soon as a new version uploads to a monitored folder. The full list of version, folder, and lineage events sits in the supported events reference. After the event fires, the file may still be being translated on the backend, so full content extraction can slightly lag the notification.
Does the BIM 360 API still work after Autodesk's rebrands?
Yes. BIM 360 API endpoints remain operationally active for legacy BIM 360 projects, and the integration targets those projects directly.
Similar integrations
Autodesk Construction Cloud (ACC): Datagrid connects ACC projects to document, cost, takeoff, and cross-platform CDE workflows.
BIM 360 Build: Datagrid automates RFIs, submittal tracking, and field process workflows, augmenting BIM 360 Docs' document management and review lifecycle.
Procore: Datagrid commonly pairs Procore with BIM 360 Docs for cross-platform RFIs, budgets, and field data.
Navisworks: Datagrid routes clash test results and coordination data into BIM 360 Docs workflows for issue triage and change-detection reporting.
PlanGrid: Datagrid syncs sheet sets, field reports, and RFIs to speed sheet distribution and on-site markups alongside BIM 360 Docs.
Oracle Primavera Cloud (OPC): Datagrid integrates schedule and risk analysis from Primavera to correlate document revisions in BIM 360 Docs with project timelines.