Delete a deploy key

Delete one of a repository's deploy keys by its id.

DELETE/repos/{owner}/{name}/keys/{id}

A machine using it can no longer clone or push. There is no editing a key: to change its title or access, delete it and add it again. Needs the Admin role on the repository. Recorded in the workspace’s audit log.

The key stops working at once. 404 when the repository has no deploy key with that id. Recorded in the workspace’s audit log as repo.deploy_key_removed.

Authentication: Required. Send an access token as Authorization: Bearer.
MCP tool: access with action remove_deploy_key, and the same inputs
Scope: An access token needs access:admin.

Path parameters

Name	Type	Required	Description
`owner`	string	Yes	The workspace that owns the repository.
`name`	string	Yes	The repository’s name.
`id`	string	Yes	The deploy key’s id (dk_…), from `list_deploy_keys`.

Example request

curl -X DELETE https://api.g1t.sh/repos/flagon-io/hello/keys/dk_01kp3g4h5j6k7m8n9p0q1r2s3t \
  -H "Authorization: Bearer $G1T_TOKEN"

Example response

A successful request answers 200 with:

true

Errors

A failed request answers with one of these statuses and a body like {"error": {"code": "not_found", "message": "Repository not found."}}. See errors.

Status	Code	When
401	`unauthenticated`	A token is required, or the one sent is not valid.
403	`forbidden`	The token is valid but not allowed to do this, such as a member-only change or an agent token outside its repository.
404	`not_found`	It does not exist, or you cannot see it.
409	`conflict`	The request conflicts with the current state.
422	`invalid`	The input is not valid. `message` says which field and why.