Delete an endpoint

Delete a Frontier Gateway endpoint and stop routing its slug.

curl

curl --request DELETE \
  --url https://api.baseten.co/v1/gateway/endpoints/abc123hash \
  --header "Authorization: Api-Key $BASETEN_API_KEY"

200

{
  "id": "abc123hash",
  "slug": "my-org/glm-5.2"
}

Delete an endpoint. The call tears down the endpoint and its targets and stops routing its slug. The slug is freed for reuse: you can POST /v1/gateway/endpoints again with the same value to provision a fresh endpoint.

Errors

Status	Meaning
403 Forbidden	The endpoint exists but isn’t in your workspace, or the caller doesn’t have management scope.
404 Not Found	No endpoint with this id in your workspace, or it has already been deleted.

curl

curl --request DELETE \
  --url https://api.baseten.co/v1/gateway/endpoints/abc123hash \
  --header "Authorization: Api-Key $BASETEN_API_KEY"

200

{
  "id": "abc123hash",
  "slug": "my-org/glm-5.2"
}

Authorizations

Authorization · string · header · required

Send Authorization: Bearer <api_key>. The legacy Authorization: Api-Key <api_key> scheme is also accepted.

Path Parameters

endpoint_id · string · required

Response

200 - application/json

id · string · required

Identifier of the deleted endpoint.

slug · string · required

Slug of the deleted endpoint.