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: remove redundant key fields table

Anshu Garg94ec0437b7fb
diff --git a/docs/content/changelog/02-06-26-webhook-subscriptions-api.mdx b/docs/content/changelog/02-06-26-webhook-subscriptions-api.mdx
index 3a0d0c25b..c17d2cd01 100644
--- a/docs/content/changelog/02-06-26-webhook-subscriptions-api.mdx
+++ b/docs/content/changelog/02-06-26-webhook-subscriptions-api.mdx
@@ -146,20 +146,6 @@ The `composio.connected_account.expired` event follows the V3 envelope format:
The `data` object matches the response from [`GET /api/v3/connected_accounts/{id}`](https://docs.composio.dev/rest-api/connected-accounts/get-connected-accounts-by-nanoid), making it easy to process with existing code and SDK types.
</Callout>
-### Key Fields
-
-| Field | Description |
-|-------|-------------|
-| `id` | Unique event identifier |
-| `timestamp` | ISO 8601 timestamp when the event was generated |
-| `type` | Always `composio.connected_account.expired` for this event |
-| `metadata.project_id` | Your project identifier |
-| `metadata.org_id` | Your organization identifier |
-| `data.id` | The connected account ID (use this to prompt re-authentication) |
-| `data.toolkit.slug` | The integration that expired (e.g., `gmail`, `slack`) |
-| `data.status` | Will be `EXPIRED` |
-| `data.status_reason` | Human-readable reason for expiration |
-
---
## Verifying Webhook Signatures