X Release Notes

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.

Today, we introduced the X API Playground — a self-hosted local server that emulates X API v2 endpoints. Develop and test integrations without making real API calls or hitting rate limits. Includes realistic mock data, state persistence, OpenAPI validation, rate-limit simulation, and a web UI. Install with go install github.com/xdevplatform/playground/cmd/playground@latest. Learn more here.

Today, we launched the new News endpoints in the X API v2:

• GET /2/news/search — returns trending news stories matching a search query
• GET /2/news/{id} — looks up a specific news story by ID

Both endpoints support news.fields for selecting fields like name, summary, contexts, cluster_posts_results, and last_updated_at_ms. Learn more here.

Today, we launched the official first-party Python and TypeScript XDKs (X Developer Kits) for the X API v2. The XDKs handle authentication (Bearer Token, OAuth 2.0 PKCE, OAuth 1.0a), automatic pagination, real-time streaming with reconnect handling, and comprehensive coverage of all v2 endpoints. Install with pip install xdk or npm install @xdevplatform/xdk. Learn more here.

Today, we added keyword filtering to X Activity API subscriptions. In addition to filtering by User ID, subscribers can now narrow event delivery further by keyword — useful for News events and other event types where high event volumes warrant additional filtering.