Key concepts
A revision belongs to a single 3D model and holds the complete, processed representation of a 3D scene. Each revision has its own node tree, which you can traverse to access individual components, assemblies, and their properties. Revisions also track processing status and can expose multiple output formats.Create revisions
Creating a revision starts a processing job. In a hybrid project, use the classic and hybrid request body. In a data modeling only project, create the revision with 3D jobs. The data-modeling-only request body on this endpoint is being retired.Nodes
List nodes after the revision status isDone. Calling a nodes endpoint earlier returns HTTP 400.
GET returns nodes in ascending treeIndex order. You can request one subtree with nodeId and limit it with depth. Set sortByNodeId to true when that order is faster for your client. The partition parameter requires sortByNodeId=true.
POST .../nodes/list filters by node name or property and supports pagination and partitions.
Outputs
A processed revision can expose more than one output. Each output is a viewer format, such as Reveal, or a format you can import into another tool. Theversion on an output identifies the format version, not the processed revision. The shape of each output depends on that format.
What you can do
- Create revisions by uploading 3D source files to a model.
- List and retrieve revisions for a given model.
- Update revision metadata and thumbnails.
- Delete revisions that are no longer needed.
- View processing logs to monitor conversion status.
- Navigate nodes by listing, filtering, and traversing the node hierarchy.
- List available outputs for a revision to discover supported formats.