Skip to main content
GET
Stream pod logs
Required API key scope: pods:read

Authorizations

Authorization
string
header
required

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.

Headers

Last-Event-ID
string<date-time>

SSE reconnect cursor — a timestamp emitted by this endpoint. Takes precedence over since and tail: when present, the stream resumes from this point. Sent automatically by EventSource on reconnect.

Path Parameters

id
string
required

Pod identifier

Query Parameters

source
enum<string>

Log source to stream. Omit to include both container and system logs. Log source to include in a log stream.

  • container — container stdout/stderr log stream
  • system — host lifecycle/userlogs stream
Available options:
container,
system
tail
integer
default:100

Number of historical lines to backfill before streaming. Defaults to 100 when omitted; set 0 to stream live with no backfill. Maximum 5000. Ignored when since or Last-Event-ID is provided — the resume cursor drives the backfill instead.

Required range: 0 <= x <= 5000
since
string<date-time>

RFC3339 timestamp to resume from. Ignored when Last-Event-ID is provided. When set, the stream resumes from this point and tail is ignored.

Response

Pod log event stream

Server-Sent Events stream. Each event includes an id: line and a JSON data: payload with source, line, and ts fields.

Last modified on November 18, 2026