curl --request GET \
--url https://{cluster}.cognitedata.com/api/v1/projects/{project}/3d/files/{threedFileId}/{subPath} \
--header 'Authorization: Bearer <token>'"<string>"Required capabilities:
threedAcl:READ
Retrieve the contents of a 3D file, for a blobId which is of a directory type. This applies to the output types ‘gltf-directory’, ‘reveal-directory’, ‘ept-pointcloud’, ‘tiles-directory’, ‘model-from-points’.
The ‘subPath’ elements, i.e. directory and/or file names, within each directory output type is subject to change and depends on each output type.
Experimental outputs, normally not enabled: The ‘tiles-directory’ output contains files for classification of the point cloud data. Retrieve the ‘tiles.json’ file from this output for a overview of the files within this output. The ‘model-from-points’ output is used for storing a mesh based output file of some parts of the point cloud. This is stored as a ‘model.ciff’ file, in the Cognite internal file format.
This endpoint supports tag-based caching.
This endpoint is only compatible with 3D file IDs from the 3D API, and not compatible with file IDs from the Files API.
curl --request GET \
--url https://{cluster}.cognitedata.com/api/v1/projects/{project}/3d/files/{threedFileId}/{subPath} \
--header 'Authorization: Bearer <token>'"<string>"Access token issued by the CDF project's configured identity provider. Access token must be an OpenID Connect token, and the project must be configured to accept OpenID Connect tokens. Use a header key of 'Authorization' with a value of 'Bearer $accesstoken'. The token can be obtained through any flow supported by the identity provider.
The blob ID of the 3D output directory.
The filename for the 3D file to retrieve.
Success
The raw contents of the file.
Was this page helpful?