Get a queued pod
Retrieve a queued Runpod Pod by ID to see whether it is still waiting for capacity, which pod it created, or why it failed.
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.
Console sessions (Clerk JWTs) act for the signed-in user. To act for a team instead, also send X-Team-Id: <team_id>; it applies only when the user owns or belongs to that team, otherwise the request runs against the user's own account. API keys created inside a team already act for that team and do not need the header.
Response
OK
A pod waiting for capacity, or the record of one that waited. It carries what identifies and schedules the request; the full container settings are not echoed back, keep your create request.
Where a queued pod is in its life.
QUEUED— waiting for capacity (fromqueue.startsAtwhen set)DEPLOYED— capacity came and a pod was created;podIdnames itFAILED— capacity came but the deploy was refused for good;failureReasonsays whyEXPIRED—queue.expiresAtpassed without capacityCANCELLED— cancelled withDELETE /v2/queued-pods/{id}
QUEUED, DEPLOYED, FAILED, EXPIRED, CANCELLED