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

# Delete Webhook

> Deletes a webhook endpoint. This action is PERMANENT. The webhook will stop receiving events immediately.

Deletes a webhook endpoint. This action is PERMANENT. The webhook will stop receiving events immediately.

## Authentication

This endpoint requires authentication via Bearer token:

* **Authorization**: `Bearer <token>`

## Path Parameters

| Parameter        | Type          | Required | Description     |
| ---------------- | ------------- | -------- | --------------- |
| `organizationId` | string (UUID) | Yes      | Organization ID |
| `id`             | string (UUID) | Yes      | Webhook ID      |

## Permissions

Only **OWNERS** and **ADMINS** can delete webhooks.

## What Happens

When a webhook is deleted:

* Webhook is **permanently removed**
* No more events will be sent to this URL
* The webhook will stop receiving events **immediately**
* This action **cannot be undone**

## Example Request

```bash theme={null}
curl -X DELETE http://localhost:3001/api/organizations/550e8400-e29b-41d4-a716-446655440000/webhooks/123e4567-e89b-12d3-a456-426614174000 \
  -H "Authorization: Bearer <your_token>"
```

## Example Response

```
Status: 204 No Content
```

A successful deletion returns no response body, only a 204 status code.

## Common Errors

### 401 Unauthorized

Authentication required.

```json theme={null}
{
  "statusCode": 401,
  "message": "Authentication required. Provide a valid bearer token."
}
```

### 403 Forbidden

Only owners and admins can delete webhooks.

```json theme={null}
{
  "statusCode": 403,
  "message": "Access denied. Only owners and admins can delete webhooks."
}
```

### 404 Not Found

Webhook not found.

```json theme={null}
{
  "statusCode": 404,
  "message": "Webhook not found with the provided ID."
}
```

## Best Practices

Before deleting a webhook:

1. **Disable it first** - Set `isActive: false` to test without deleting
2. **Check delivery history** - Review recent deliveries
3. **Notify your team** - Coordinate with developers using this webhook
4. **Document the change** - Keep track of why it was removed


## OpenAPI

````yaml DELETE /organizations/{organizationId}/webhooks/{id}
openapi: 3.1.0
info:
  title: Timbrix API
  description: >-
    REST API with OAuth2 server for managing organizations, members, and
    webhooks
  version: '1.0'
  contact: {}
servers:
  - url: http://sandbox.mintlify.com
    description: Sandbox environment
  - url: http://localhost:3001/api
    description: Local development
security: []
tags:
  - name: organizations
    description: Organization management endpoints
  - name: oauth
    description: OAuth2 authentication and authorization
  - name: webhooks
    description: Webhook configuration and delivery
  - name: users
    description: User information endpoints
  - name: api-keys
    description: API Keys management and validation
paths:
  /organizations/{organizationId}/webhooks/{id}:
    delete:
      tags:
        - webhooks
      summary: Delete webhook
      description: >-
        Deletes a webhook endpoint. This action is PERMANENT. The webhook will
        stop receiving events immediately.
      operationId: WebhooksController_delete
      parameters:
        - name: organizationId
          required: true
          in: path
          schema:
            type: string
        - name: id
          required: true
          in: path
          schema:
            type: string
      responses:
        '204':
          description: Webhook deleted successfully. Webhook will no longer receive events.
        '401':
          description: Authentication required. Provide a valid bearer token.
        '403':
          description: Access denied. Only owners and admins can delete webhooks.
        '404':
          description: Webhook not found with the provided ID.
      security:
        - bearer: []
components:
  securitySchemes:
    bearer:
      scheme: bearer
      bearerFormat: JWT
      type: http

````