Skip to main content
The 3D files API provides direct access to processed 3D file data stored in CDF. You can retrieve individual files or navigate directory structures for a given 3D file ID. These endpoints are typically used by 3D visualization tools to load model geometry, textures, and associated resources.

​
Key concepts

When CDF processes a 3D model revision, it generates optimized output files (geometry, textures, metadata) that are stored as 3D files. Each file has a unique ID and may contain sub-paths for directory-like navigation. Visualization clients use these endpoints to stream 3D content efficiently.

​
Output types

These endpoints accept 3D file IDs from the 3D API. A Files API ID does not work. Retrieve by ID supports tag-based caching for ciff-processed, ciff-partially-processed, and node-property-metadata-json. Use the sub-path endpoint when the output is a directory: gltf-directory, reveal-directory, ept-pointcloud, tiles-directory, or model-from-points. Directory and file names inside an output can change. Start from the descriptor in that output:
  • gltf-directory and reveal-directory include scene.json, which lists the other files. Reveal v3 and later uses gltf-directory. Reveal v1 and v2 use reveal-directory.
  • ept-pointcloud includes ept.json and ept-hierarchy/0-0-0-0.json. Point files live under ept-data as .bin files.

​
What you can do

  • Retrieve a single 3D file by its ID.
  • Navigate directory structures within a 3D file using sub-paths.
These endpoints return binary data and are primarily intended for use by 3D rendering applications, not for direct user interaction.
Last modified on November 2, 2026