Skip to content

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(changelog): show endpoint response shape after step 2

Anshu Garge62a2aeb856c
diff --git a/docs/content/changelog/04-20-26-webhook-triggers-v2.mdx b/docs/content/changelog/04-20-26-webhook-triggers-v2.mdx
index 701da14d8..2a48f67e6 100644
--- a/docs/content/changelog/04-20-26-webhook-triggers-v2.mdx
+++ b/docs/content/changelog/04-20-26-webhook-triggers-v2.mdx
@@ -72,7 +72,20 @@ curl -X POST "https://backend.composio.dev/api/v3/webhook_endpoints" \
-d '{ "toolkit_slug": "slack", "client_id": "YOUR_SLACK_CLIENT_ID" }'
```
-The response includes `webhook_url`. The call is idempotent.
+Sample response:
+
+```json
+{
+ "id": "we_abc123",
+ "toolkit_slug": "slack",
+ "client_id": "YOUR_SLACK_CLIENT_ID",
+ "webhook_url": "https://backend.composio.dev/api/v3/webhook_ingress/slack/we_abc123/trigger_event",
+ "data": null,
+ "created_at": "2026-04-20T10:00:00.000Z"
+}
+```
+
+Hold on to two values from the response: `id` (used as `ENDPOINT_ID` in the next steps) and `webhook_url` (the URL you'll paste into your Slack app dashboard in step 5). The call is idempotent — calling it again with the same `toolkit_slug` and `client_id` returns the existing endpoint.
### 3. Store the signing secret