Skip to main content
curl --request DELETE \
  --url https://api.baseten.co/v1/gateway/groups/abc123hash \
  --header "Authorization: Api-Key $BASETEN_API_KEY"

{
  "id": "abc123hash",
  "metadata": {
    "name": "Acme prod",
    "external_entity_id": "cust_42"
  },
  "deleted_at": "2026-05-13T12:34:56Z"
}

Documentation Index

Fetch the complete documentation index at: https://docs.baseten.co/llms.txt

Use this file to discover all available pages before exploring further.

Delete a group. The call removes the group, revokes every API key in the group, and recursively removes every descendant group and their keys. The group’s external_entity_id is freed for reuse: you can POST /v1/gateway/groups again with the same value to provision a fresh group. To revoke a single key without churning the whole group, use Revoke an API key instead.

​
Authentication

​
Authorization
string
required
Workspace API key with management scope, formatted as Api-Key <your-key>.

​
Path parameters

​
group_id
string
required
Internal Baseten ID of the group to delete.

​
Response

​
id
string
required
Internal ID of the deleted group.
​
metadata
object
required
Group identity at the time of deletion. Same shape as on Create a group.
​
deleted_at
string
required
RFC 3339 UTC timestamp of deletion.
Descendant groups are soft-deleted in the same transaction but aren’t included in the response body. Their keys are revoked and their model attachments are removed.

​
Errors

StatusMeaning
403 ForbiddenThe group exists but isn’t in your workspace, or the caller doesn’t have management scope.
404 Not FoundNo group with this id in your workspace, or it has already been deleted.
curl --request DELETE \
  --url https://api.baseten.co/v1/gateway/groups/abc123hash \
  --header "Authorization: Api-Key $BASETEN_API_KEY"

{
  "id": "abc123hash",
  "metadata": {
    "name": "Acme prod",
    "external_entity_id": "cust_42"
  },
  "deleted_at": "2026-05-13T12:34:56Z"
}