diff --git a/changelog.mdx b/changelog.mdx
index c1db3554d..1591a2d82 100644
--- a/changelog.mdx
+++ b/changelog.mdx
@@ -7,6 +7,28 @@ keywords: ["changelog", "API updates", "release notes", "what's new", "API chang
 
 To subscribe to updates, please [**“Turn on notifications”**](https://help.x.com/en/managing-your-account/notifications-on-mobile-devices#:~:text=In%20the%20top%20menu,%20you,you%20would%20like%20to%20receive) for [**@API**](https://x.com/api). You can also follow this changelog in your feed reader via the [**RSS feed**](https://docs.x.com/changelog/rss.xml).
 
+<Update label="Aug 29, 2026" description="X API v2">
+  ### Broadcast lifecycle events in the X Activity API
+
+  We added `broadcast.start` and `broadcast.end` events to the [X Activity API](/x-api/activity/introduction). Subscribe by User ID to be notified in real time when a user starts or ends a live broadcast. Both are public events, so you can subscribe with either app-only or user-context authentication.
+
+  ### Filter qualifiers for X Activity API subscriptions
+
+  X Activity API subscriptions now accept an optional `filter.qualifiers` map to narrow which events match, with up to 8 entries per subscription. Currently supported: `conversation_type` (`direct`, `group`) on `chat.received`, and `direction` (`inbound`, `outbound`) on `follow.follow`, `follow.unfollow`, and `like.create`. Unsupported keys or values return a 400 error. Learn more in the [Filter qualifiers](/x-api/activity/introduction#filter-qualifiers) section.
+
+  ### Credit balance endpoint
+
+  We added [`GET /2/usage/credits`](/x-api/usage/get-usage-credits), which returns your Pay-Per-Use credit balance in USD. Use it to monitor remaining credits programmatically.
+
+  ### `is_subscriber` field on `broadcast.chat` events
+
+  The `broadcast.chat` event payload in the [X Activity API](/x-api/activity/event-payloads) now includes an `is_subscriber` boolean indicating whether the message author is a subscriber of the broadcaster.
+
+  ### Trends by WOEID: `tweet_count` removed
+
+  `GET /2/trends/by/woeid/{woeid}` does not return `tweet_count`, and the field has been removed from the `trend.fields` parameter and response schema. The endpoint returns `trend_name` only. The `/2/users/personalized_trends` endpoint is unaffected and still returns `tweet_count`.
+</Update>
+
 <Update label="Aug 13, 2026" description="X Ads API">
   ### Updated `video_total_views` definition