01
Documented
Data Management API
APS documents access to supported projects, folders, items, versions, metadata, uploads, and downloads.
Autodesk / Construction documents, models, and project management
Evaluate Autodesk Forma and Autodesk Platform Services by current and former product names, module, project, data region, record type, permission boundary, and exact API or event surface.
What it is designed to do
Coordinating construction documents, models, project information, reviews, cost, issues, and related Autodesk construction workflows across configured products.
Best suited for
Design and construction teams using Autodesk Docs or other Autodesk Construction Cloud modules as important project-information environments.
Buyer boundary
This profile explains documented product and integration surfaces. It is not an endorsement, procurement recommendation, guarantee of compatibility, or substitute for checking the buyer’s product, edition, region, licences, configuration, terms, permissions, and workflow.
Normal operating records
Autodesk may remain authoritative for approved document versions, model-derived information, and module-specific project records. A derived object table or downloaded model representation is not automatically the accepted BIM or project record.
Typical AEC uses
Records and information
Hub, project, folder, item, and version
File metadata and storage reference
AEC model element and parameter
Issue, review, or cost record where supported
BuildingConnected event or record where supported
Documented access routes
A vendor interface establishes a possible technical route. It does not establish record authority, downstream security, correct mapping, complete processing, accepted output, or permission to act.
Documented
APS documents access to supported projects, folders, items, versions, metadata, uploads, and downloads.
Documented
APS webhooks can notify subscribers about supported events. Event availability differs across services and modules.
Documented
GraphQL access can expose supported project structures, files, Revit elements, parameters, and change records.
Product-dependent
Availability depends on the Autodesk product, entitlement, region, project configuration, and required data boundary.
Native IDs and crosswalks
Identity, permission, and authority
Known implementation limits
Crosswalk Autodesk Docs to Forma Data Management, BIM Collaborate Pro to Forma Design Collaboration, Autodesk Build to Forma Build, and Autodesk Takeoff to Forma Takeoff. Treat BIM 360, former Autodesk Construction Cloud names, current Forma products, desktop products, and APS interfaces as related but distinct environments, then confirm the buyer's entitlement, module, region, project, interface, and retained legacy references.
API and webhook coverage differs by Autodesk product and module
The 2026 Forma naming transition does not by itself change project data, APIs, integrations, entitlement, or source authority
Some interfaces, exports, contracts, and procedures may retain former Autodesk Construction Cloud names
A model element API does not turn derived data into authoritative BIM
File-change notification does not establish review or approval status
Licensing, region, entitlement, and data residency must be confirmed
Where StructuredLayer may connect it
The actual implementation boundary is confirmed from the buyer's product, workflow, records, permissions, difficult cases, required direction, consequences, and acceptance conditions.
Crosswalk Autodesk project and document identities to operating records
Monitor approved file, review, issue, cost, or bid events where supported
Create document and model metadata indexes with source links
Route changed versions for impact review
Keep accepted BIM, document-control, and professional decisions in their authorised systems
Questions before scope
Which Autodesk products and modules are deployed?
Which region and tenant contain the records?
Are files, model elements, issues, reviews, cost, or bids in scope?
Which version or approval state is authoritative?
What qualified review is required before downstream use?
Official vendor documentation
Features, endpoints, scopes, licences, regions, plans, limits, and vendor terms can change. The implementation must confirm the current documentation for the buyer's actual environment.
Related system profiles
Primary operating system
Project execution and construction records
Inspect profileSpecialist system
Drawing, PDF, markup, Session, and Project collaboration
Inspect profilePrimary operating system
Document libraries, lists, mail, collaboration, and identity context
Inspect profileAutodesk Forma (formerly Autodesk Construction Cloud) and one workflow
Bring the exact product, module, environment, workflow, records, users, permissions, required access direction, current failure, and intended buyer decision.
Next best page
Move from evaluating the operating conditions to choosing a bounded response and assessing one real workflow.