Delete an artifact for good
Delete an artifact in the trash, and everything under it, for good: its content and versions are gone and cannot be restored.
POST
/workspaces/{workspace}/artifacts/{artifact_id}/purgeMove it to the trash first. Takes full access (manage).
Only an artifact in the trash can be deleted for good: trash_workspace_artifact first.
- Authentication: Required. Send an access token as
Authorization: Bearer. - MCP tool:
artifactwithactionpurge, and the same inputs - Scope: An access token needs
artifacts:admin.
Path parameters
Section titled “Path parameters”| Name | Type | Required | Description |
|---|---|---|---|
workspace |
string | Yes | The workspace’s slug, e.g. “acme”. |
artifact_id |
string | Yes | The artifact’s id (fol_…), or its address: /acme/-/artifacts/q4-roadmap-fol_… |
Example request
Section titled “Example request”curl -X POST https://api.g1t.sh/workspaces/acme/artifacts/fol_01kq8d5f7h9k1n3q5s7u9w1y3a/purge \ -H "Authorization: Bearer $G1T_TOKEN"Example response
Section titled “Example response”A successful request answers 200 with:
{ "deleted": true}Errors
Section titled “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. |