Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
docs(triggers): point Webhooks API links to specific create operations
The /reference/api-reference/webhooks page lists both Subscriptions and Endpoints operations on one page, so the generic page-level link was ambiguous about which API the prose was referring to. Each label now points to its create operation page (postWebhookSubscriptions / postWebhookEndpoints). Also moves the Webhook Endpoints API pointer up out of Step 2 into the section intro so it scopes the whole walkthrough. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Anshu Garg committed
May 11, 2026 at 12:36 UTC
0006e1032335b6b2e052b9e249633a55d8cf715a
4 files changed
+5
-7
docs/content/changelog/02-06-26-webhook-subscriptions-api.mdx
+1
-1
@@ -19,7 +19,7 @@ A new API for managing webhook configurations with event filtering, HMAC signatu
19
20
## API Overview
21
22
-See the [API Reference](/reference/api-reference/webhooks) for complete details.
22
+See the [Webhook Subscriptions API Reference](/reference/api-reference/webhooks/postWebhookSubscriptions) for complete details.
23
24
### Endpoints
25
docs/content/docs/glossary.mdx
+2
-2
@@ -124,11 +124,11 @@ A specific, active trigger scoped to a user's connected account.
124
</GlossaryTerm>
125
126
<GlossaryTerm name="Webhook Endpoint">
127
-The ingress URL Composio issues per OAuth app for webhook triggers, plus the signing secret used to verify each inbound request. Composio configures it for you in most cases. When a trigger type's `requires_webhook_endpoint_setup` flag is true, you configure it yourself once per OAuth app via the [Webhook Endpoints API](/reference/api-reference/webhooks). See [Configuring the webhook endpoint](/docs/setting-up-triggers/creating-triggers#configuring-the-webhook-endpoint).
127
+The ingress URL Composio issues per OAuth app for webhook triggers, plus the signing secret used to verify each inbound request. Composio configures it for you in most cases. When a trigger type's `requires_webhook_endpoint_setup` flag is true, you configure it yourself once per OAuth app via the [Webhook Endpoints API](/reference/api-reference/webhooks/postWebhookEndpoints). See [Configuring the webhook endpoint](/docs/setting-up-triggers/creating-triggers#configuring-the-webhook-endpoint).
128
</GlossaryTerm>
129
130
<GlossaryTerm name="Webhook Subscription">
131
-The URL Composio delivers signed events to in your application. One per project, configured via the dashboard or the [Webhook Subscriptions API](/reference/api-reference/webhooks). See [Subscribing to events](/docs/setting-up-triggers/subscribing-to-events).
131
+The URL Composio delivers signed events to in your application. One per project, configured via the dashboard or the [Webhook Subscriptions API](/reference/api-reference/webhooks/postWebhookSubscriptions). See [Subscribing to events](/docs/setting-up-triggers/subscribing-to-events).
132
</GlossaryTerm>
133
134
<GlossaryTerm name="User ID">
docs/content/docs/setting-up-triggers/creating-triggers.mdx
+1
-3
@@ -41,7 +41,7 @@ Every inbound event is signature-checked at ingress before any trigger fires:
41
**Sharing one OAuth app across projects?** Consolidate to a single project or register separate OAuth apps per project before continuing.
42
</Callout>
43
44
-The walkthrough below uses Slack as the example. For setup notes specific to each toolkit, see its FAQ section — e.g., [Slack](/toolkits/slack), [Notion](/toolkits/notion).
44
+The walkthrough below uses Slack as the example and walks through the [Webhook Endpoints API](/reference/api-reference/webhooks/postWebhookEndpoints). For setup notes specific to each toolkit, see its FAQ section — e.g., [Slack](/toolkits/slack), [Notion](/toolkits/notion).
45
46
### Step 1: Discover what credentials the endpoint needs
47
@@ -76,8 +76,6 @@ Sample response:
76
77
### Step 2: Create the endpoint
78
79
-Call the [Webhook Endpoints API](/reference/api-reference/webhooks) with the toolkit slug and your OAuth `client_id`:
80
-
79
```bash
80
curl -X POST "https://backend.composio.dev/api/v3.1/webhook_endpoints" \
81
-H "x-api-key: <YOUR_COMPOSIO_API_KEY>" \
docs/content/docs/setting-up-triggers/subscribing-to-events.mdx
+1
-1
@@ -14,7 +14,7 @@ Webhooks are the recommended way to receive trigger events in production. To sta
14
| `composio.connected_account.expired` | Fired when a connected account expires and needs re-authentication. See [Subscribing to connection expiry events](/docs/subscribing-to-connection-expiry-events). |
15
| `composio.trigger.disabled` | **Fired when** Composio automatically disables a trigger — expired connection, webhook refresh failure, or unhealthy polling. **Not fired when** you disable a trigger through the manage API or deactivate its connected account via `PATCH /api/v3/connected_accounts/{id}/status`. |
16
17
-Set your webhook URL in the [dashboard settings](https://platform.composio.dev?next_page=/settings/webhook) or via the [Webhook Subscriptions API](/reference/api-reference/webhooks):
17
+Set your webhook URL in the [dashboard settings](https://platform.composio.dev?next_page=/settings/webhook) or via the [Webhook Subscriptions API](/reference/api-reference/webhooks/postWebhookSubscriptions):
18
19
```bash
20
curl -X POST https://backend.composio.dev/api/v3.1/webhook_subscriptions \