DELETE /gammas/{gammaId}

Delete a Gamma document. Requires a workspace admin role on the API key's workspace.

Delete a Gamma document. Gamma archives it automatically first if needed, then marks it for deletion.

Delete a Gamma

delete

Deletes a Gamma document. Requires workspace admin role on the workspace the API key belongs to. The Gamma is auto-archived first if not already archived, so a single call handles the full archive-then-delete transition. The Gamma becomes immediately inaccessible and is removed from all workspace views. After deletion, the Gamma is no longer addressable via the API; subsequent requests for the same ID return the same response as for a non-existent Gamma.

Authorizations

X-API-KEYstringRequired

API key for authentication

Path parameters

gammaIdstringRequired

The unique ID of the Gamma to delete

Example: gamma_abc123

Responses

200

Gamma deleted successfully

application/json

statusstring · enumRequired

Status of the deletion request. Always deleted on success.

Possible values:

gammaIdstringRequired

The ID of the deleted Gamma

Example: gamma_abc123

messagestringRequired

Customer-facing message confirming the Gamma has been deleted.

400

Invalid request parameters

401

Invalid or missing API key

403

Access denied - workspace admin role required

delete/v1.0/gammas/{gammaId}

DELETE /v1.0/gammas/{gammaId} HTTP/1.1
Host: public-api.gamma.app
X-API-KEY: YOUR_API_KEY
Accept: */*

{
  "status": "deleted",
  "gammaId": "gamma_abc123",
  "message": "text"
}

Deletion requires a workspace admin role on the API key's workspace. A successful response returns status: deleted. The Gamma becomes immediately inaccessible and is no longer addressable via the API.

Related

• GET /generations/{id} to retrieve the gammaId from a completed generation
• POST /gammas/{gammaId}/archive if you want to archive without deleting
• Error codes for authentication and permission failures