Event reference
Find an event family, then open its full payload and integration guide.
Tweet content
Use tweet/content as the first usable post, then branch on author.platform.
Route by platform
Read the post key from (author.platform, tweetId). If platform is absent, use twitter.
Read references
Keep referenced posts and their attachments under ref; each nested reference has its own tweetId.
Enrichment metadata
Replace the metadata at (platform, tweetId) with each tweet/meta snapshot. Do not keep fields missing from the new snapshot.
Tweet updates
Patch only fields present in tweet/update; do not replace the whole post.
Match the post
Match every update with (platform, tweetId).
Replace reference snapshots
If an update contains ref, replace the stored reference with that snapshot.
Complete optional fields
Treat present poll, article, and media values as complete replacements for those fields.
Tweet lifecycle
Apply delete, pin, and unpin to the stored post without overwriting its content.
Account events
Route profile, follow, unfollow, and affiliate changes under the account family.
Route account operations
Branch on op; ignore unknown operations without closing the socket.
Store affiliate relationships
Apply the action to (organization.id, member.id) and use eventId only for an exact replay.
Replay stored changes
Use type=PROFILE, FOLLOW, or AFFILIATE with the History API.
Callouts
Selected accounts emit structured account/callout events on the same WebSocket.
Select accounts
Add a pump.fun username, Solana wallet, or profile URL in the Callouts tab.
Route the event
Handle initial account/callout content and later account/callout_update enrichment. Read the caller and token address before optional fields.
Use identifiers
Deduplicate by envelope id. Merge enrichment into d.updateOf, including nested fields, without another alert.
Charity events
Enabled charity alerts emit live-only charity/added events.
News articles
Enabled publications emit news/article; stored articles use the separate News History API.
Select publications
Read and update the enabled publication set before filtering live events.
Read live articles
Use the envelope id for idempotency and keep source.id with the article.
Page through history
Pass nextCursor back unchanged until it is null.
Event sequence
Use an idempotent local projection; the WebSocket envelope does not contain a sequence number.
Receive content
Store the first usable content event.
Replace enrichment
Replace each live metadata snapshot by post key.
Apply lifecycle
Apply lifecycle operations to the same post.
Control messages
Use auth_pong for connection state and twitter_handles_result for command outcomes.
Handle management channel
Follow or unfollow monitored Twitter handles over the handle-management WebSocket or REST API.