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
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Anshu Garg committed
Feb 6, 2026 at 14:01 UTC
94ec0437b7fb8b7512fa1da453e46429efca2bc2
1 file changed
-14
docs/content/changelog/02-06-26-webhook-subscriptions-api.mdx
-14
@@ -146,20 +146,6 @@ The `composio.connected_account.expired` event follows the V3 envelope format:
146
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.
147
</Callout>
148
149
-### Key Fields
150
-
151
-| Field | Description |
152
-|-------|-------------|
153
-| `id` | Unique event identifier |
154
-| `timestamp` | ISO 8601 timestamp when the event was generated |
155
-| `type` | Always `composio.connected_account.expired` for this event |
156
-| `metadata.project_id` | Your project identifier |
157
-| `metadata.org_id` | Your organization identifier |
158
-| `data.id` | The connected account ID (use this to prompt re-authentication) |
159
-| `data.toolkit.slug` | The integration that expired (e.g., `gmail`, `slack`) |
160
-| `data.status` | Will be `EXPIRED` |
161
-| `data.status_reason` | Human-readable reason for expiration |
162
-
149
---
150
151
## Verifying Webhook Signatures