Skip to main content

Export an asset

Use result.asset.id from the finished job as ASSET_ID (or a ready variation’s assetId). format is a query parameter and there is no request body. The response is the file itself, not JSON or a link. Each request exports one asset in one format. Exports are free and you can download the same asset as often as you like. Check the HTTP status and Content-Type before saving the body, so an error message never ends up saved as an asset file. Content-Disposition suggests a filename. X-Export-Warnings lists anything worth knowing about the export.

What is in the GLB bundle

A successful job means the asset was built and published. It is not a guarantee that every physics check passed; read physics-qa.json when it is present.

Load collision geometry

In collision.glb, each mesh node is one convex hull. Load every node as its own hull and do not re-decompose it. Assets with functional openings also include collision_hybrid_convex.glb and collision_hybrid_sdf.glb. Use that pair instead of collision.glb, and load the second file as SDF colliders. (PhysX SDF colliders do not collide with plane shapes, so use a box for the floor or table.) physics.json describes each file under colliders. In ManiSkill:

Asset details

GET /v1/assets/{asset_id}?include_record=true returns the full record: parts, joints and materials. Mesh and texture URLs inside it expire after five minutes, so read the record again when you need fresh ones, and keep the asset ID as your permanent identifier.

Team downloads

Team keys have two extra options, when enabled for the Team: Team exports return the files saved when the asset was built. A format the Team has not enabled returns 409 export_not_available; check published_formats on the job or batch item first. An asset that has not finished returns 409 asset_not_ready. Binary downloads include an X-Content-SHA256 header you can verify.

Endpoint reference

Export an asset · Download a saved file · Get a temporary download link