Delete a tunnel

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

Delete a tunnel and revoke its token and certificates. Agents and saved requests that reference it fail with 404 tunnel_not_found from then on, so remove those references first.

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

{
  "id": "tnl_01JCE4G6J8L0N2Q4S6U8",
  "type": "tunnel",
  "deleted": true
}

Examples

curl -sS -X DELETE "https://app.syntic.ai/v1/tunnels/tnl_01JCE4G6J8L0N2Q4S6U8" \
  -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.
409conflict_errortunnel_in_useAn agent definition or the organization’s MCP policy names this tunnel; details lists where.
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?