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

# Delete Trigger

> Delete a trigger from an integration

<Info>
  **Using our API via a dedicated deployment?** Just replace `api.langdock.com` with your deployment's base URL: **`<deployment-url>/api/public`**
</Info>

Permanently deletes a trigger from an integration. This action cannot be undone.

## Required Scopes

This endpoint requires the `INTEGRATION_API` scope.

## Path Parameters

| Parameter       | Type   | Required | Description                   |
| --------------- | ------ | -------- | ----------------------------- |
| `integrationId` | string | Yes      | UUID of the integration       |
| `triggerId`     | string | Yes      | UUID of the trigger to delete |

## Example

```javascript theme={null}
const axios = require("axios");

async function deleteTrigger(integrationId, triggerId) {
  const response = await axios.delete(
    `https://api.langdock.com/integrations/v1/${integrationId}/triggers/${triggerId}`,
    {
      headers: {
        Authorization: "Bearer YOUR_API_KEY"
      }
    }
  );

  console.log("Trigger deleted:", response.data);
}

deleteTrigger("550e8400-e29b-41d4-a716-446655440000", "660e8400-e29b-41d4-a716-446655440001");
```

## Response Format

### Success Response (200 OK)

```typescript theme={null}
{
  message: "Trigger deleted";
  id: string;  // UUID of the deleted trigger
}
```

## Error Handling

| Status Code | Description                              |
| ----------- | ---------------------------------------- |
| 400         | Invalid integration or trigger ID format |
| 401         | Invalid or missing API key               |
| 403         | No access to this integration            |
| 404         | Integration or trigger not found         |
| 429         | Rate limit exceeded                      |

<Warning>
  Deleting a trigger is permanent and cannot be undone. Any workflows using this trigger will no longer be activated by it.
</Warning>

<Info>
  Langdock intentionally blocks browser-origin requests to protect your API key and ensure your applications remain secure. For more information, please see our guide on [API Key Best Practices](/en/admin/ai-adoption-and-rollout/best-practices/api-key-best-practices).
</Info>