Sandboxes
Get a sandbox
Retrieve a Runpod sandbox by ID with its lifecycle state, compute, cost per hour, timeout deadlines, labels, and termination reason if it has stopped.
GET
Returns a single sandbox by ID. Terminated sandboxes remain readable, with
state, terminationReason, and terminatedAt set.
RUNNING means the backing compute is allocated, not that the container has finished pulling and started. A sandbox can report RUNNING for a short while (typically 10 to 30 seconds) before it accepts commands.
Path parameters
string
required
The sandbox ID.
Response
string
required
Unique sandbox identifier.
string
required
Human-readable name. Not required to be unique.
enum<string>
required
Current lifecycle state:
CREATING, RUNNING, TERMINATED, or FAILED.string | null
Template the sandbox was created from, if any.
string | null
Container image the sandbox runs, if it was created from an image.
string | null
CPU flavor backing the sandbox.
object
The compute currently backing the sandbox. Absent while the sandbox is
CREATING and after it’s TERMINATED.integer
required
Seconds of inactivity after which the sandbox is terminated, after any clamping to the account maximum.
integer
required
Maximum total lifetime in seconds, after any clamping to the account maximum.
string<date-time>
required
Time of the most recent recorded activity.
string<date-time>
required
Time after which the sandbox is terminated for inactivity if no further activity occurs.
string<date-time>
required
Time after which the sandbox is terminated for reaching its maximum lifetime.
object
User-supplied string key-value labels.
string | null
Why the sandbox was terminated.
null while the sandbox is alive.string<date-time> | null
When the sandbox was terminated.
null while the sandbox is alive.string<date-time>
required
When the sandbox was created.
string<date-time>
required
When the sandbox was last updated.
Errors
Last modified on September 29, 2026