X Developer Updates & Release Notes

Mute and block events for X Activity API

Today, we added mute and block events to the X Activity API. You can now subscribe by User ID to receive real-time notifications when a user mutes or unmutes (mute.mute, mute.unmute) or blocks or unblocks (block.block, block.unblock) another user.

These are private events: they require user-context (OAuth 2.0) authentication with the mute.read or block.read scope, respectively, and the user_id filter matches the user performing the action.

Articles draft and publish endpoints

Today, we added new endpoints for drafting and publishing Articles via the X API.

Today, we added post.create and post.delete events to the X Activity API. You can now subscribe by User ID to receive real-time notifications when a user creates or deletes a Post.

For basic per-user post activity, use XAA. For advanced keyword filtering and the full set of Filtered Stream operators, continue to use the Filtered Stream.

Added support for the paid_partnership Post field

When creating a Post via POST /2/tweets, set "paid_partnership": true to indicate the Post is a paid partnership (i.e., the author is disclosing that it contains paid promotion). The Post will be labeled as a paid promotion.

When reading Posts, request tweet.fields=paid_partnership to retrieve the value (true if the author has disclosed the Post as containing paid promotion).

Today, we migrated the X API v2 search endpoints (/2/tweets/search/recent, /2/tweets/search/all, /2/tweets/counts/recent, /2/tweets/counts/all) to the new X core platform search index. This brings major performance improvements, dramatically fewer 503 errors, and three new precision operators: min_likes:, min_replies:, and min_reposts:. Note: retweets are no longer returned in keyword-based search results (the Filtered Stream is unchanged). Learn more here.

Today, we announced the deprecation of POST /2/account_activity/replay/webhooks/{webhook_id}/subscriptions/all, effective March 25, 2026 at 12:00 PM ET. Use the new consolidated POST /2/webhooks/replay endpoint instead — it provides identical functionality. Learn more here.

Today, we added an optional direction filter to X Activity API subscriptions. Subscribers can now scope DM and chat events to sent, received, or both, reducing noise when only outgoing or incoming events are needed.

Today, we announced changes to event type naming in the X Activity API, effective March 18, 2026. PascalCase event types (e.g., ProfileBioUpdate) are being deprecated in favor of a dot-separated lowercase format (e.g., profile.update.bio). Update any filtering, switch statements, or deserialization logic that relies on the old values. Learn more here.

Today, we added legacy DM events (dm.received, dm.sent, dm.read, dm.indicate_typing) to the X Activity API. This brings DM event delivery from the Account Activity API into the lower-latency XAA pipeline.

Today, we made changes to reduce automated, low-quality replies on X.

Programmatic replies via POST /2/tweets are now only permitted when the original Post’s author has “summoned” the replier (by @mentioning that account or quoting one of its Posts).

Additional restrictions apply to programmatically @mentioning or quoting users.

These changes affect self-serve tiers only — Enterprise access is not impacted.

Learn more here.

Today, we added Spaces lifecycle events (spaces.start, spaces.end) to the X Activity API.

Subscribe by User ID to be notified in real time when a Space starts or ends.

Today, we deprecated the min_likes, min_replies, and min_reposts operators on /2/tweets/search/recent and /2/tweets/search/all. This change does not affect the equivalent operators in the Filtered Stream. We are evaluating how to best re-enable these in the future. Learn more here.

Today, we added full OAuth 2.0 support to the Account Activity API v2. Developers can now create subscriptions using OAuth 2.0 with fine-grained scopes (e.g., follow.read) instead of the all-or-nothing OAuth 1.0a permission model. Existing OAuth 1.0a-based integrations continue to work without disruption — when present, OAuth 1.0a permissions fully override OAuth 2.0 scopes. Learn more here.