Assets must have
status: "ready" before they can be added to a scene. See the Assets API for generation and polling details.Create a Scene
A human-readable name for the scene. Example:
"Warehouse Workcell Alpha".An optional description of the scene’s purpose or configuration.
POST /scenes — Response
Unique identifier for the scene. Use this in all subsequent scene operations.
The name provided at creation.
The description provided at creation, or
null if omitted.ISO 8601 timestamp of scene creation.
Array of placed assets in the scene. Empty on creation.
Example Response
Get Scene Details
Retrieve a scene and its full list of placed assets, including each asset’s position and rotation in the scene coordinate frame.Path Parameters
The unique identifier of the scene.
GET /scenes/{id} — Response
Unique scene identifier.
Scene name.
Scene description.
Array of placed-asset objects. Each entry includes:
Example Response
List Scenes
Return a paginated list of all scenes associated with your API key.Query Parameters
Maximum number of scenes to return. Defaults to
20. Maximum is 100.Number of scenes to skip. Defaults to
0.GET /scenes — Response
Array of scene summary objects, each with
id, name, description, and created_at.Total number of scenes in your account.
The
limit applied to this response.The
offset applied to this response.Example Response
Add an Asset to a Scene
Place a ready asset into a scene at a specified position and orientation. You can add the same asset multiple times at different poses (e.g. two identical gripper arms mounted on opposite sides of a workcell).Path Parameters
The unique identifier of the scene.
Body Parameters
The ID of the asset to add. The asset must have
status: "ready".Position of the asset in scene-space. Defaults to the origin
{x: 0, y: 0, z: 0} if omitted.Orientation of the asset expressed as a unit quaternion. Defaults to identity
{x: 0, y: 0, z: 0, w: 1} (no rotation) if omitted.POST /scenes/{id}/assets — Response
Returns the full updated scene object, including the newly placed asset appended to the assets array.
Example Response
Export a Scene
Export the entire scene — all placed assets combined — as a single simulator-ready file. This is the recommended way to load a complete environment into Isaac Sim or MuJoCo, as it preserves all relative transforms between assets.Path Parameters
The unique identifier of the scene to export.
Body Parameters
The export format. Supported scene export formats:
| Value | Description |
|---|---|
isaac_sim_usd | USD stage containing all scene assets, for NVIDIA Isaac Sim |
mujoco_mjcf | Single MJCF XML file with all assets included as bodies, for MuJoCo |
POST /scenes/{id}/export — Response
A pre-signed URL to download the exported scene file. Time-limited — download promptly.
ISO 8601 timestamp indicating when the
download_url expires.Example Response
Scene export bundles all constituent assets into a single file. Every asset in the scene must have
status: "ready" — if any asset is still pending or processing, the export request will return a 400 Bad Request error.