Overview
What is BIM 360 Build: BIM 360 Build is Autodesk's cloud-based field and project management product for general contractors, specialty contractors, and owners. It centralizes RFIs, submittals, issues, checklists, safety observations, assets, cost items, and related project records so project teams can manage execution in a single environment.
How to integrate BIM 360 Build with Datagrid
You configure the integration once, authorize Autodesk access, and define how often Datagrid should sync project data. The steps below follow that setup path for BIM 360 Build.
Configure the connector
Open Datagrid and go to Settings > Connectors > Add New.
Search for BIM 360 Build in the connector library.
Click Connect and sign in with your Autodesk credentials when prompted.
Select the BIM 360 account and projects you want to sync.
Choose your data endpoints (Issues, RFIs, Assets, Cost Items, Documents, and others).
Set your ingestion schedule: one-time pull, daily, or event-triggered only for supported object types.
Confirm permissions and click Save.
Authorize Autodesk access
The integration authenticates via OAuth 2.0 through Autodesk Platform Services (APS). Datagrid handles the token exchange automatically. Your BIM 360 Account Admin must authorize Datagrid's Client ID under Account Admin > Custom Integrations before the connection will return data, a one-time provisioning step required by Autodesk.
A typical two-legged token exchange against the APS authentication endpoint looks like this:
curl -X POST https://developer.api.autodesk.com/authentication/v2/token \
-H "Content-Type: application/x-www-form-urlencoded" \
-u "<CLIENT_ID>:<CLIENT_SECRET>" \
-d "grant_type=client_credentials&scope=data:read data:write account:read"
A successful response returns a bearer token that Datagrid uses on every subsequent BIM 360 API call:
{
"access_token": "eyJhbGciOi...",
"token_type": "Bearer",
"expires_in": 3599
}
Define sync behavior
The list below shows the main sync characteristics for this integration.
Direction: Primarily BIM 360 Build to Datagrid, with selective write-back only for supported endpoints; some objects are read-only or project-type-dependent.
Data objects: Commonly synced objects include Issues, RFIs, Assets, Cost Items, Checklists (read-only), Documents, Locations, Project Users, and Companies; objects such as Submittals are project-type-dependent.
Sync frequency: Configurable as on-demand, scheduled (e.g., daily), or event-triggered only for object types with supported webhook surfaces.
Format: JSON via REST API; bulk CSV via Data Connector API for analytics use cases.
A typical RFI payload returned from the BIM 360 RFIs endpoint looks like this:
{
"id": "abc123",
"subject": "Clarification on slab penetration detail",
"status": "open",
"priority": "high",
"assigned_to": "user_456",
"due_date": "2026-06-15",
"spec_section": "03 30 00",
"created_at": "2026-05-28T14:22:00Z"
}
Once this setup is complete, Datagrid can keep BIM 360 Build data flowing into the workflows your project teams already run.
Why use BIM 360 Build with Datagrid
Project teams already capture critical execution data in BIM 360 Build. Datagrid turns that data into completed workflows, escalations, and reporting without forcing teams back into manual exports and inbox triage.
Automated RFI routing and prioritization: Agents parse incoming RFIs, cross-reference project specs and historical data, and route each RFI to the right party in seconds instead of hours (source).
Cross-project reporting without manual exports: Datagrid ingests data from multiple BIM 360 projects and aggregates it into portfolio-level dashboards. Operations leaders get visibility they cannot pull from single-project views.
Submittal gap detection: Agents compare submittal logs against spec books and flag missing items before they become change orders or schedule delays.
Safety compliance monitoring on autopilot: Expired certifications, unresolved safety observations, and new incidents trigger automated alerts. Project teams stay informed without manual tracking (source).
Zero double-entry across systems: Scheduled syncs move RFIs, submittals, cost data, and project records from BIM 360 into ERPs, accounting tools, and scheduling systems automatically. Version conflicts and duplicate data entry disappear.
Field-queryable agents: Project teams ask agents questions from the field and receive answers with linked source documents, without needing full platform access (source).
What you can build with BIM 360 Build Datagrid integration
Project teams use BIM 360 Build to capture records, and Datagrid executes the workflows around them. The examples below show how this integration can enforce standards across RFIs, submittals, reporting, and risk review:
RFI processing and intelligent routing pipeline: Connect BIM 360 RFI data to Datagrid on a daily schedule.
Automated daily progress reports with schedule variance alerts: Datagrid pulls project records and schedule milestones from BIM 360 Build.
Cross-platform submittal tracking and gap analysis: Autodesk's AI capability, AutoSpecs, processes spec books uploaded to BIM 360 as PDFs and uses machine learning to extract submittal requirements and identify missing submittal items before they become costly errors.
Portfolio-level risk scoring from aggregated issue data: Datagrid ingests issues, safety observations, checklists, and subcontractor assignments from BIM 360 projects across a region or business unit.
Resources and documentation
BIM 360 API overview on Autodesk Platform Services
BIM 360 API basics and core concepts, including container ID architecture and project type detection
OAuth 2.0 authentication guide for understanding two-legged vs. three-legged token flows
BIM 360 API provisioning tutorial for authorizing third-party app access
RFIs API tutorial for understanding RFI data structure and workflow types
Data Connector field guide for bulk CSV extraction of Issues, Submittals, Cost, and RFI data
ACC API compatibility guide for project-type differences between BIM 360 and ACC/Forma APIs
Frequently asked questions
What BIM 360 Build data objects can Datagrid access?
Commonly supported objects include Issues, RFIs, Assets, Cost Items, Documents, Locations, Project Users, and Companies. Checklists are read-only. Some objects, especially Submittals, have important compatibility differences between project types. The full list of available endpoints is on the Datagrid BIM 360 Build connector page.
Does the connector work if my organization has migrated from BIM 360 to Autodesk Construction Cloud or Forma?
BIM 360 Build is an older product name, and API surfaces are not identical across project types. If you have both BIM 360 and ACC/Forma projects, consult the ACC API compatibility guide for specifics.
What authentication method does the BIM 360 Build connector use?
The connector uses OAuth 2.0 via Autodesk Platform Services, and Datagrid manages the token exchange. The Account Admin authorization step described in the setup section is the most common blocker for first-time setup.
Similar integrations
Procore: Complementary platform for project and financial management frequently synced with BIM 360 Build for cross-system reporting and workflows.
BIM360 Docs: Document management companion used to sync plans, versions, and files between BIM 360 Build and downstream analytics or QA workflows.
Revit: BIM authoring tool that produces models and metadata consumed by BIM 360 Build for coordination, extract, and agent-driven model insights.
Navisworks: Model coordination and clash detection tool whose outputs feed BIM 360 Build coordination and issue workflows.
BuildingConnected: Preconstruction and bid management platform whose bid and subcontractor data complements BIM 360 Build procurement and risk workflows.
Browse by category
Construction
BIM
Project management
Integrations