List all sandboxes
Returns sandboxes belonging to the authenticated team, ordered by creation time (newest first) by default.
Pagination, sorting, and search
Pass limit (and offset) to fetch one page at a time; the
X-Total-Count response header reports the total across all pages.
Omitting limit returns the full list, so existing unpaginated
callers are unaffected. Sort with sort + order, filter by exact
status, and search names with q (case-insensitive substring).
Filtering by metadata
Any query parameter prefixed metadata. is treated as a filter
clause: ?metadata.env=prod&metadata.owner=agent-7. Multiple
filters AND together — a sandbox matches only if every key/value
pair is present in its metadata. Values are compared as exact
strings; there is no type coercion or substring matching.
Authorizations
Query Parameters
Filter sandboxes whose metadata contains an exact {key}: <value>
pair. Repeat with different keys to AND multiple filters. Values
are always strings. Example: ?metadata.env=prod.
Case-insensitive substring match on the resource name.
Filter by exact sandbox status. Unknown values are a 400.
starting, active, pausing, paused, resuming, failed, deleted Column to sort by (paired with order).
created_at, name, status Sort direction applied to sort.
asc, desc Maximum rows to return (page size). Omit to return the full list unpaginated — the default, preserved for backward compatibility with callers that page client-side. Values above 200 are clamped to 200.
1 <= x <= 200Rows to skip before the page. Combine with limit to paginate.
x >= 0Response
List of sandboxes belonging to the authenticated team
Public sandbox ID: a bare UUID, or the region-tagged form sb-<region>-<uuid> (e.g. sb-use-1b4e28ba-…). Treat as an opaque string; the tagged form routes the request to the sandbox's home region. Endpoints accept both forms interchangeably.
^(sb-[a-z0-9]+-)?[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$Current state of the sandbox. active means running; paused means paused and awaiting resume. resuming is a transient state observed while the platform restores a paused sandbox (e.g. via auto-resume on /exec); clients should retry shortly.
active, paused, resuming ID of the latest snapshot (present after a pause).
Auto-pause timeout in seconds, if configured. Absent when auto-pause is disabled.
Garbage-collection window for the paused state, if configured. Absent when auto-delete is disabled.
When the sandbox will be deleted. Present only while the sandbox is paused with auto_delete_seconds configured. The deadline is armed when the sandbox pauses (or when the setting is applied to an already-paused sandbox) and cleared on resume.
Current egress allow/deny rules, if any have been configured. Absent when the sandbox uses default network settings.
User-supplied tags attached at creation. Always present — sandboxes created without metadata return {} rather than being absent.
Default access for newly published ports. public and private
are strict modes; existing published rows keep their own access.
legacy_public may be returned for an older sandbox and preserves
all-port behavior until updated to a strict mode.
legacy_public, public, private