Skip to main content
DELETE
Archive an AI gateway
Sets the gateway’s status to archived and returns the updated gateway.
Archiving a gateway does not archive its agents. Each agent keeps its own status. Since 2026-08-27 an agent under an archived gateway is refused with 503 gateway_not_active, so traffic does stop — but the agent rows are still active, and un-archiving the gateway resumes them. If you mean to retire the agents, archive them individually.
Archiving also disables the upstream routes rows it orphans, scoped to the data space you archived in — so archiving a sandbox agent does not disable the Live route. Before 2026-08-30 the routes stayed enabled, which left the upstream reachable through a gateway you had archived.
The dashboard twin. The same operation exists on the admin host as DELETE /admin/ai-gateway/{gatewayId}, session-authenticated with an X-Tenant-ID header and an owner/admin role. That is what the dashboard itself calls. Prefer the /v1 operation above for anything you write: it is the surface the five SDKs, the Postman collection and this spec cover.

Authorizations

Authorization
string
header
required

OAuth 2.1 authentication — recommended for new integrations. Access tokens (kc_ prefix) are minted at the root-host token endpoint https://api.knoxcall.com/oauth/token and passed as Authorization: Bearer <access_token>. Public clients must use PKCE with the authorization_code grant; confidential clients may use client_credentials. The first-party SDKs and the knoxcall login CLI handle token minting, caching, refresh, and DPoP for you.

Path Parameters

id
string<uuid>
required

The AI gateway UUID.

Response

The archived gateway.

data
object
meta
object

Metadata included with every API response.