List tunnel connections

⚠️
Preview — this feature is being built; the design below is the spec.
GET https://app.syntic.ai/v1/tunnels/{tunnel_id}/connections

Return the connector instances currently attached to a tunnel: where they connect from, their version and traffic. Run two or more connectors for redundancy; requests are spread across them.

For how this fits into a full workflow, see MCP tunnels.

Headers

HeaderRequiredValue
AuthorizationYesBearer <key>: a private inference key (sk_live_...). See Authentication.
syntic-betaYes, while in previewmcp-tunnels-2026-12-01. Without it the call fails with 400 beta_required. See Versioning.

Path parameters

ParameterTypeDescription
tunnel_idstringThe tunnel id, starting with tnl_.

Response

200 OK, Content-Type: application/json

{
  "data": [
    {
      "connection_id": "conn_01JD9BK3M5P7R9T1V3X5",
      "connector_version": "0.9.2",
      "remote_ip": "198.51.100.17",
      "connected_at": "2026-11-05T06:12:00Z",
      "last_seen_at": "2026-11-05T10:00:31Z",
      "requests_1h": 1820,
      "errors_1h": 3
    }
  ],
  "has_more": false
}
FieldTypeDescription
remote_ipstringThe public address the connector dials out from.
requests_1hintegerMCP requests forwarded in the last hour.

Examples

curl -sS "https://app.syntic.ai/v1/tunnels/tnl_01JCE4G6J8L0N2Q4S6U8/connections" \
  -H "Authorization: Bearer $SYNTIC_API_KEY" \
  -H "syntic-beta: mcp-tunnels-2026-12-01"

Errors

Errors use the error envelope and carry a request_id. Codes specific to this operation:

StatustypecodeWhen
400invalid_request_errorbeta_requiredThe syntic-beta header is missing.
404not_found_errortunnel_not_foundNo tunnel with this id in the key’s workspace.
401authentication_errorinvalid_api_keyThe key is missing, unknown, revoked or expired.
429rate_limit_errorrate_limitedToo many requests; wait for Retry-After. See Rate-limit headers.
Was this page helpful?