Delete a label (tenant:forge:write and maintainer, or tenant:forge:admin)
DELETE /api/forge/v1/projects/{key}/labels/{id}
Module: Forge · operationId: deleteForgeLabel · Tag: Configuration · Auth: access token (Authorization: Bearer <accessToken>)
Same permission as creating. A row other configuration or items still reference answers 409 in_use with details.counts (for a section definition the items with content in it); deleting a label or an empty section takes it off the items. Automations are not counted and not rewritten – one that names a deleted or renamed label fails its run (invalid, field label, in its log). The label of an ownership (scope owner) goes only with its ownership (409 in_use, details.counts.ownerships, which also counts ownerships matching a label); no other label may be created in or renamed into that scope (400 name), and an ownership's label keeps its name (409 ownership_label). An item type an ownership matches is 409 in_use (details.counts.ownerships); a team owning an ownership too, and an ownership with children.
Parameters
| Name | In | Type | Required | Description |
|---|---|---|---|---|
key |
path | string | yes | Project key (e.g. APP) |
id |
path | string (uuid) | yes |
Responses
- 204 Deleted
- 403 Error (
application/json) - 404 Error (
application/json) - 409 Error (
application/json)
Example request
curl -X DELETE 'https://api.mbcom.cloud/api/forge/v1/projects/string/labels/3f2b8c1e-7d4a-4e9b-9c2a-5b1d6e8f0a12' \
-H "Authorization: Bearer $ACCESS_TOKEN"