---
title: "Get Tunnel Status Endpoint"
method: GET
path: "/api/v1/tunnel/{tunnel_id}"
tags: ["Tunnel"]
---

# Get Tunnel Status Endpoint

`GET /api/v1/tunnel/{tunnel_id}`

Get status of a specific tunnel.

## Path parameters

- `tunnel_id` string, required

## Response `200`

Successful Response

- TunnelStatusResponse — Response containing tunnel status information.
  - `tunnel_id` string, required — Unique tunnel identifier
  - `name` string, nullable — Friendly name if set
  - `status` 'pending' | 'connected' | 'disconnected' | 'expired' | 'terminated', required
  - `hostname` string, required — Tunnel hostname
  - `url` string, required — Full HTTPS URL
  - `local_port` integer, required — Local port forwarded by the tunnel
  - `labels` string[] — Tunnel labels
  - `http_user` string, nullable — HTTP basic auth username, if auth is enabled
  - `auth_enabled` boolean — Whether HTTP basic auth protects tunnel traffic
  - `created_at` string, date-time, required — Tunnel creation time
  - `connected_at` string, date-time, nullable — When the client connected
  - `expires_at` string, date-time, required — Token expiration time
  - `terminated_at` string, date-time, nullable — When the tunnel was terminated
  - `user_id` string, required — Owner user ID
  - `team_id` string, nullable — Team ID if applicable

## Other responses

- `401` — Authorization failed
- `422` — Invalid request data

---

[API](https://skmtc.net/primeintellect/apis/pi-api.md) · [All operations](https://skmtc.net/primeintellect/apis/pi-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/primeintellect/pi-api/versions/60efc9b3ff2a/schema)