> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gable.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Delete a tag definition.

> Delete a USER tag definition, removing it from the vocabulary. The read path drops field tags whose definition is gone, so the tag stops rendering on the next read with no sweep to run.

202 rather than 204 because this is not a purge: the events that labelled fields stay in the log, so what this deletes is the vocabulary entry. SYSTEM tags cannot be deleted at all; deactivate them with PUT instead.



## OpenAPI

````yaml /api-reference/bundled.yaml delete /v0/tags/{tagId}
openapi: 3.1.0
info:
  title: Gable API
  description: >
    API to interact with the Gable platform

    ## Authorization

    All API requests require an API key to be passed in the `X-API-KEY` header.
    For instructions on finding your API key and api endpoint check out the [API
    Key documentation](../docs/api-keys.md).

    Example: `curl -H "X-API-KEY: <your-api-key>"
    https://api-{organization}.gable.ai/v0/ping`
  contact:
    name: Gable Engineering
    url: https://gable.ai
    email: engineers@gable.ai
  version: 1.54.0
servers:
  - url: https://{hostname}.gable.ai
    description: Gable API
    variables:
      hostname:
        default: demo-api
        description: Customer environment assigned by Gable
security:
  - ApiKeyAuth: []
tags:
  - name: action
  - name: api-keys
  - name: auth
  - name: changelog
  - name: config
  - name: debug
  - name: settings
  - name: slack
  - name: sso
  - name: webhook
  - name: notifications
  - name: telemetry
  - name: component
  - name: components
  - name: sca
  - name: cross-service-components
  - name: lineage
  - name: events
  - name: measurements
  - name: defect-report
  - name: data-tagging
    description: Tag vocabulary management and field level tagging of lineage boundaries.
paths:
  /v0/tags/{tagId}:
    delete:
      tags:
        - data-tagging
      summary: Delete a tag definition.
      description: >-
        Delete a USER tag definition, removing it from the vocabulary. The read
        path drops field tags whose definition is gone, so the tag stops
        rendering on the next read with no sweep to run.


        202 rather than 204 because this is not a purge: the events that
        labelled fields stay in the log, so what this deletes is the vocabulary
        entry. SYSTEM tags cannot be deleted at all; deactivate them with PUT
        instead.
      operationId: deleteTag
      parameters:
        - in: path
          name: tagId
          required: true
          schema:
            type: string
          description: The tag definition id.
      responses:
        '202':
          description: >-
            The definition was removed and reads no longer show the tag.
            Accepted rather than completed, because the tag's events remain in
            the log.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/DeleteTagResponse'
        '404':
          description: No definition exists under that id.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '409':
          description: >-
            The definition is a SYSTEM tag, which cannot be deleted: deactivate
            it with PUT instead. Also returned when concurrent vocabulary writes
            lose the version condition three times.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '500':
          description: Internal Server Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
components:
  schemas:
    DeleteTagResponse:
      type: object
      description: >-
        Acknowledgement that a tag definition was removed from the vocabulary.
        The read path drops field tags whose definition is gone, so the tag
        stops rendering on the next read with no sweep to wait for.


        202 rather than 204 because this is not a purge: the add and remove
        events that labelled fields stay in the event log, so recreating a tag
        under the same id makes them count again.
      properties:
        tag_id:
          type: string
          description: The id whose definition was removed from the vocabulary.
      required:
        - tag_id
      additionalProperties: false
    ErrorResponse:
      type: object
      required:
        - message
      properties:
        id:
          type: number
        title:
          type: string
        message:
          type: string
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: X-API-KEY

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.