@devries-cameron20 / composio-1 / commits / 0f6b0883a
Fork 0

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: polish webhook subscriptions changelog

- Rename section to API Overview with link to API reference - Rename Requirements to Notes - Simplify recommended actions - Clarify auto-migration includes composio.trigger.message by default Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Anshu Garg committed Feb 6, 2026 at 13:57 UTC 0f6b0883ab142e3e89db5218af12324386547c37
1 file changed +4 -5
docs/content/changelog/02-06-26-webhook-subscriptions-api.mdx
+4 -5
@@ -19,6 +19,8 @@ A new API for managing webhook configurations with event filtering, HMAC signatu
19
20 ## API Overview
21
22 +See the [API Reference](https://docs.composio.dev/rest-api/webhook-subscriptions) for complete details.
23 +
24 ### Endpoints
25
26 | Method | Endpoint | Description |
@@ -69,7 +71,7 @@ curl -X POST "https://backend.composio.dev/api/v3/webhook_subscriptions" \
71 The `secret` is only returned once at creation time or when rotated. Store it securely for signature verification.
72 </Callout>
73
72 -### Requirements
74 +### Notes
75
76 - **1 subscription per project**: Currently limited to one webhook subscription per project. This will be expanded in future releases.
77 - **HTTPS required**: Webhook URLs must use HTTPS in production environments.
@@ -214,8 +216,7 @@ The following legacy endpoints are deprecated and will be removed in a future re
216
217 ### What We've Done For You
218
217 -- **Automatic migration**: We've created a webhook subscription for all existing projects that had webhook URLs configured
218 -- **No duplicate deliveries**: Legacy and new systems don't send duplicate webhooks
219 +- **Automatic migration**: We've created a webhook subscription for all existing projects that had webhook URLs configured, with `composio.trigger.message` enabled by default
220 - **Same payload format**: If you were using V1, V2, or V3 triggers, they continue with the same format
221
222 ### What Continues to Work
@@ -231,8 +232,6 @@ While not required, we recommend migrating to benefit from:
232
233 1. **Event filtering**: Only receive events you care about
234 2. **New events**: Access `composio.connected_account.expired` (V3 only)
234 -3. **Better secret management**: Rotate secrets without downtime
235 -4. **Future features**: New events will only be available via subscriptions
235
236 ---
237