Enable a V2 tunnel for an existing running Devbox. Tunnels provide encrypted URL-based access to the Devbox without exposing internal IDs. The tunnel URL format is: https://{port}-{tunnel_key}.tunnel.runloop.ai
Each Devbox can have one tunnel.
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
The Devbox ID.
Configuration for creating a V2 tunnel. When specified at Devbox creation, a tunnel will be automatically provisioned.
Authentication mode for the tunnel. Defaults to 'public' if not specified.
open, authenticated When true, HTTP traffic through the tunnel counts as activity for idle lifecycle policies, resetting the idle timer. Defaults to true if not specified.
When true, HTTP traffic to a suspended devbox will automatically trigger a resume. Defaults to false if not specified.
OK
A V2 tunnel provides secure HTTP access to services running on a Devbox. Tunnels allow external clients to reach web servers, APIs, or other HTTP services running inside a Devbox without requiring direct network access. Each tunnel is uniquely identified by an encrypted tunnel_key and can be configured for either open (public) or authenticated access. Usage: https://{port}-{tunnel_key}.tunnel.runloop.ai
The encrypted tunnel key used to construct the tunnel URL. URL format: https://{port}-{tunnel_key}.tunnel.runloop.{domain}
The authentication mode for the tunnel.
open, authenticated Creation time of the tunnel (Unix timestamp milliseconds).
When true, HTTP traffic through the tunnel counts as activity for idle lifecycle policies, resetting the idle timer.
When true, HTTP traffic to a suspended devbox will automatically trigger a resume.
Bearer token for tunnel authentication. Only present when auth_mode is 'authenticated'.