Autodesk BIM 360
Autodesk BIM 360 is a cloud-based construction project management platform that provides a comprehensive suite of REST APIs enabling developers to integrate construction workflows into custom applications. The platform supports managing projects, documents, issues, RFIs, submittals, quality checklists, assets, cost management, and field reports throughout the construction lifecycle. BIM 360 APIs use OAuth 2.0 authentication through Autodesk Platform Services (APS) and allow teams to automate project setup, synchronize data with external systems, and extend platform capabilities. The APIs cover account administration, document management, model coordination, and field management, making it a central hub for construction data integration and workflow automation.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Autodesk BIM 360 the way a machine reads it — 46 machine-readable artifacts across 25 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Autodesk BIM 360 scores 52.7/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Autodesk BIM 360
Each block below is one kind of artifact we hold for Autodesk BIM 360. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 25
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
BIM 360 Account Admin API
Automates setting up projects, assigning project admins, managing member and partner company directories, and synchronizing data with external systems. Enables programmatic cont...
BIM 360 Issues API
Creates, tracks, and updates issues within BIM 360 projects. Issues are items created for tracking, managing, and communicating problems and other points of concern through to r...
BIM 360 Document Management API
Connects BIM APIs to access, upload, and share 2D plans, 3D BIM models, and any other project documents to maximize collaboration. Provides programmatic access to BIM 360 Docs f...
BIM 360 Assets API
Creates and manages assets in the BIM 360 Assets service, allowing developers to define settings such as categories, custom attributes, and sets of statuses. Provides full progr...
BIM 360 Cost Management API
Provides access to cost and budget changes within construction projects, including budget, contract, and change order information. Enables integration with financial systems and...
BIM 360 Model Coordination API
Provides full access to model coordination services used by the BIM 360 Model Coordination web application. Enables detection and management of clashes and issues that arise whe...
BIM 360 RFIs API
Creates, tracks, and updates RFIs (Requests for Information) within BIM 360 projects. Provides programmatic access to the RFI workflow, enabling integration with external projec...
BIM 360 Checklists API
Creates and tracks quality checklists within BIM 360 projects. Supports field inspection workflows and quality assurance processes by providing programmatic access to checklist ...
BIM 360 Data Connector API
Retrieves aggregated data from BIM 360 services including Admin, Issues, Locations, Submittals, Cost, and RFIs. Enables bulk data extraction for analytics, reporting, and integr...
BIM 360 Locations API
Manages and shares the hierarchy of building areas within construction projects. Provides programmatic access to location trees used to organize and contextualize issues, assets...
BIM 360 Relationships API
Creates, retrieves, and deletes links between entities across domains in BIM 360. Enables cross-domain data linking between issues, RFIs, assets, documents, and other project en...
Autodesk BIM 360 Account Users API
The Account Users API from Autodesk BIM 360 — 6 operation(s) for account users.
Autodesk BIM 360 Business Units API
The Business Units API from Autodesk BIM 360 — 1 operation(s) for business units.
Autodesk BIM 360 Companies API
The Companies API from Autodesk BIM 360 — 7 operation(s) for companies.
Autodesk BIM 360 Issue Attachments API
The Issue Attachments API from Autodesk BIM 360 — 3 operation(s) for issue attachments.
Autodesk BIM 360 Issue Attribute Definitions API
The Issue Attribute Definitions API from Autodesk BIM 360 — 1 operation(s) for issue attribute definitions.
Autodesk BIM 360 Issue Attribute Mappings API
The Issue Attribute Mappings API from Autodesk BIM 360 — 1 operation(s) for issue attribute mappings.
Autodesk BIM 360 Issue Comments API
The Issue Comments API from Autodesk BIM 360 — 1 operation(s) for issue comments.
Autodesk BIM 360 Issue Root Cause Categories API
The Issue Root Cause Categories API from Autodesk BIM 360 — 1 operation(s) for issue root cause categories.
Autodesk BIM 360 Issue Types API
The Issue Types API from Autodesk BIM 360 — 1 operation(s) for issue types.
Autodesk BIM 360 Issues API
The Issues API from Autodesk BIM 360 — 2 operation(s) for issues.
Autodesk BIM 360 Issues Profile API
The Issues Profile API from Autodesk BIM 360 — 1 operation(s) for issues profile.
Autodesk BIM 360 Project Users API
The Project Users API from Autodesk BIM 360 — 3 operation(s) for project users.
Autodesk BIM 360 Projects API
The Projects API from Autodesk BIM 360 — 3 operation(s) for projects.
Autodesk BIM 360 User Projects API
The User Projects API from Autodesk BIM 360 — 1 operation(s) for user projects.
Scroll within the panel for all 25 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Autodesk Bim360 Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Autodesk Bim360 Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Autodesk Bim360 Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Autodesk BIM 360 API Rules
SPECTRALJSON Schema 9
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
attachment
JSON SCHEMABusinessUnit
JSON SCHEMAcomment
JSON SCHEMACompany
JSON SCHEMAIssue
JSON SCHEMAProject
JSON SCHEMAProjectUser
JSON SCHEMARole
JSON SCHEMAUser
JSON SCHEMAScroll within the panel for all 9 ·
Examples 3
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Autodesk Bim360 User Example
EXAMPLESecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Autodesk BIM 360 — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/autodesk-bim360 · machine-readable index on apis.io