Pods
Terminate a pod
Permanently terminates and deletes a pod. This is irreversible:
compute is released, any mounts.persistent host-local storage is
destroyed with it (a mounts.network volume is only detached — the
volume itself is not deleted), and the pod no longer appears in
listPods.
DELETE
Terminate a pod
Authorizations
Runpod API key authentication. Generate an API key in the Runpod console and send it in the Authorization header as Bearer <api_key>. Keys are scoped to the permissions granted when created; requests may return 403 when a valid key lacks access to the requested resource or action.
Path Parameters
Pod identifier
Response
Deleted. Response has no body.
Previous
Update a podPartially updates a pod's configuration. This is a PATCH: only the
fields present in the body are changed, and omitted fields are left
untouched. Use empty values only when you explicitly mean to clear a
field (for example, set `registry` to `null` or set `ports` to `[]`).
See `UpdatePodRequest` for the full body.
Mutable fields: `name`, `image`, `args`, `disk`, `ports`, `env`,
`registry`, `mounts`, `locked`, and `globalNetworking`. Some changes
apply immediately while others (e.g. `globalNetworking`) take effect
on the pod's next start/restart, as noted on the individual fields.
Returns `200` with the full updated pod.
Next
Terminate a pod