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

# Delete a subscription

> Unsubscribe from a Tilta webhook event type. After deletion, Tilta stops delivering events of that type to your registered endpoint.

Unsubscribing stops all future event deliveries for the specified event type or prefix. Any events already queued at the moment of deletion may still be delivered, but no new events are dispatched. To resume receiving events of this type later, [create a new subscription](/api-reference/webhooks/create-subscription).

<Warning>
  Deleting a subscription is irreversible, and the associated `signature_key` is discarded with it. To pause deliveries
  temporarily instead, [replace the subscription](/api-reference/webhooks/replace-subscription) with a `destination_url` that
  returns `2xx` without processing the payload.
</Warning>

<Note>
  Deleting a parent-prefix subscription (e.g. `FACILITY`) removes the single subscription for that prefix. It does **not**
  cascade to delete any separate leaf-event subscriptions you may have created under the same namespace (e.g. a distinct
  `FACILITY.CREATION.ACCEPTED` subscription). Delete each subscription individually if needed.
</Note>


## OpenAPI

````yaml POST /v1/webhooks/{type}/unsubscribe
openapi: 3.0.0
info:
  version: 0.0.1
  title: Tilta API
  description: Tilta API documentation
servers:
  - url: https://api.tilta.io
    description: Tilta Production API
  - url: https://api.tilta-sandbox.io
    description: Tilta Sandbox API
security: []
paths:
  /v1/webhooks/{type}/unsubscribe:
    post:
      tags:
        - Webhooks
      summary: Delete webhook subscription
      description: Unsubscribe the specified Webhook.
      parameters:
        - schema:
            type: string
            enum:
              - BUYER
              - BUYER.CREATED
              - BUYER.UPDATED
              - FACILITY
              - FACILITY.CREATION
              - FACILITY.CREATION.ACCEPTED
              - FACILITY.CREATION.IN_REVIEW
              - FACILITY.CREATION.REJECTED
              - FACILITY.EXPIRED
              - FACILITY.FROZEN
              - FACILITY.INCREASE
              - FACILITY.INCREASE.ACCEPTED
              - FACILITY.INCREASE.IN_REVIEW
              - FACILITY.INCREASE.REJECTED
              - FACILITY.RENEWAL
              - FACILITY.RENEWAL.ACCEPTED
              - FACILITY.RENEWAL.IN_REVIEW
              - FACILITY.RENEWAL.REJECTED
              - FACILITY.UNFROZEN
              - INVOICE
              - INVOICE.CLOSED
              - INVOICE.CREATED
              - INVOICE.DUE
              - INVOICE.FILE
              - INVOICE.FILE.CREATED
              - INVOICE.FILE.DELETED
              - INVOICE.FILE.REPLACED
              - INVOICE.FINANCING
              - INVOICE.FINANCING.PAID_OUT
              - ORDER
              - ORDER.CANCELLED
              - ORDER.CLOSED
              - ORDER.CONFIRMED
              - ORDER.DISBURSED
              - ORDER.EXPIRED
            description: >-
              The webhook's type. Supports the hierarchical dot-notation
              taxonomy; subscribing to a parent (e.g. `FACILITY`) implicitly
              subscribes to every descendant event (e.g.
              `FACILITY.CREATION.ACCEPTED`). Other valid values include
              `ORDER.CONFIRMED` and `INVOICE.DUE`.
            example: FACILITY.CREATION.ACCEPTED
          required: true
          name: type
          in: path
      responses:
        '200':
          description: ''
          content:
            application/json:
              schema:
                type: object
                properties:
                  destination_url:
                    type: string
                    format: uri
                    description: >-
                      Where the webhook should be sent to. This must be an
                      endpoint that handles POST requests.
                required:
                  - destination_url
                additionalProperties: false
        '400':
          description: ''
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/badRequestSchema'
        '401':
          description: ''
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/unauthorizedRequestSchema'
      security:
        - bearerAuth: []
components:
  schemas:
    badRequestSchema:
      type: object
      properties:
        code:
          type: string
          description: Error code
          example: BAD_REQUEST
        error:
          type: string
          description: Error message for debugging purposes
          example: Request validation failed. 1 issue found.
        issues:
          type: array
          items:
            type: object
            properties:
              code:
                type: string
                description: Issue code
                example: INVALID_TYPE
              path:
                type: string
                description: Issue path starting with body, params, querystring, or headers
                example: body.registered_at
              message:
                type: string
                description: Issue message for debugging purposes
                example: Invalid type
            required:
              - code
              - path
              - message
          description: List of issues
          example:
            - code: INVALID_TYPE
              path: body.registered_at
              message: Invalid type
      required:
        - code
        - error
        - issues
      description: Bad Request, see error message for details.
      example:
        code: BAD_REQUEST
        error: Request validation failed. 1 issue found.
        issues:
          - code: INVALID_TYPE
            path: body.registered_at
            message: Invalid type
    unauthorizedRequestSchema:
      type: object
      properties:
        error:
          type: string
          description: Error details.
          example: Unauthorized
        code:
          type: string
          description: Error code.
          example: UNAUTHORIZED
      required:
        - error
        - code
      description: Unauthorized Request.
      example:
        error: Unauthorized
        code: UNAUTHORIZED
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: Your Tilta API key, sent as `Bearer <key>`.

````