Get a serverless endpoint
Retrieve a Runpod Serverless endpoint by ID with its compute, worker, scaling, container, storage, and current status settings.
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
Reusable container configuration shared across templates, pods, and serverless endpoints. Adding a field here automatically propagates to all three resources.
The container's command, as a single raw string. This is the field entrypoint and cmd encode into, exposed in its stored form.
Two shapes are accepted. A bare shell string is treated as CMD and split into arguments, which is what the console's "Container start command" field writes. A JSON object of the form {"entrypoint":[...],"cmd":[...]} sets either or both explicitly.
Responses always return both representations: args exactly as stored, plus the deconstructed entrypoint and cmd. Supplying args together with entrypoint or cmd is allowed only when they describe the same command, so a read-modify-write client can send back everything it received. Send "" to clear, omit to leave unchanged.
"--model meta-llama/Llama-3-8B --max-model-len 8192"
"{\"entrypoint\":[\"/bin/bash\",\"-c\"],\"cmd\":[\"python -u main.py\"]}"
""
The tags on this resource that are visible to the caller. Keys and values are returned exactly as stored. Tags under the reserved runpod: prefix, such as the cost center, are never listed here. Absent when the resource's tags are unavailable to the caller; an empty array means none are visible.
Request-routing semantics for a modern serverless endpoint.
QUEUE— submit asynchronous or synchronous jobs through the managed queue.LOAD_BALANCER— send requests directly to worker-defined HTTP paths. Configure viaenv:PORT(server port, default 80),PORT_HEALTH(health-check port, default 80), andHEALTH_CHECK_PATH(path the load balancer polls for worker health, default/ping).
QUEUE, LOAD_BALANCER Request URLs appropriate to the endpoint's top-level type.
Queue-based endpoints provide job submission and management URLs;
load-balancing endpoints provide base and health because their
remaining paths are worker-defined.
Request and response bodies for the queue-based URLs are documented in the serverless operation reference. Load-balancing endpoints are documented in Load balancing endpoints.
- Option 1
- Option 2