Skip to content

Commit fc390f8

Browse files
committed
scuba
1 parent ce3e3a4 commit fc390f8

File tree

2 files changed

+29
-1
lines changed

2 files changed

+29
-1
lines changed

x-api/activity/introduction.mdx

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -84,6 +84,8 @@ Chat events pertain to the new, encrypted messaging stack, or XChat.
8484
| --- | --- | --- |
8585
| `chat.received` | Fired when a user receives an encrypted direct message | `user_id` |
8686
| `chat.sent` | Fired when a user sends an encrypted direct message | `user_id` |
87+
| `chat.conversation_join` | Fired when a user joins an encrypted chat conversation | `user_id` |
88+
8789

8890
### News Events
8991

x-api/webhooks/introduction.mdx

Lines changed: 27 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,8 @@ These are the products that currently support delivering events via webhook:
3434

3535
| Product | Description |
3636
|:--------|:------------|
37-
| [Account Activity API (AAA)](/x-api/account-activity/introduction) | Receive real-time account activity events (posts, DMs, follows, likes, etc.) |
37+
| [X Activity API (XAA)](/x-api/activity/introduction) | Receive real-time events for activity happening on X (open beta) |
38+
| [Account Activity API (AAA)](/x-api/account-activity/introduction) | Receive real-time events tied to specific user accounts |
3839
| [Filtered Stream Webhooks](/x-api/webhooks/stream/introduction) | Receive filtered stream Posts via webhook delivery |
3940

4041
---
@@ -93,6 +94,31 @@ X's webhook-based APIs provide two methods for confirming the security of your w
9394

9495
---
9596

97+
## Webhook validation
98+
99+
A CRC check is sent to your webhook in the following cases:
100+
101+
- Immediately upon creation
102+
- On an explicit PUT request (`PUT /2/webhooks/{id}`)
103+
- Periodically every 30 minutes, but only if the webhook has not been successfully validated in the past 24 hours
104+
105+
A webhook is marked as **invalid** when:
106+
107+
- It returns an invalid response to a CRC check
108+
- Returns a 2XX status code but the `response_token` is incorrect
109+
- Returns a 3XX status code
110+
- Results in an SSL exception
111+
- It experiences persistent transient errors such that it has not successfully validated for more than 28 hours (includes a 4-hour grace period for transient issues)
112+
- The following responses are treated as transient errors:
113+
- 4XX status code
114+
- 5XX status code
115+
- Request timeout
116+
- Channel closed
117+
118+
You can check the valid/invalid status of a webhook using the `GET /2/webhooks` endpoint or via the toolbox in the Developer Console.
119+
120+
---
121+
96122
## Getting started
97123

98124
<Note>

0 commit comments

Comments
 (0)