Skip to content

Draft changelog: Chat API bots, Activity API qualifiers, PPU #348

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mintlify wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Draft changelog: Chat API bots, Activity API qualifiers, PPU #348

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions changelog.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,24 @@ 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 28, 2026" description="X API v2">
### Bots for the X Chat API

This week, we added Bots endpoints to the [X Chat API](/xchat/introduction). You can now create programmatic bot accounts that belong to your project and manage them end to end: create a bot with `POST /2/bots`, list your project's bots, update a bot's handle, display name, or DM permission, rotate or revoke its bearer token, and delete it. All six endpoints use OAuth 2.0 app-only authentication. See the [Bots guide](/xchat/bots) and the [API reference](/x-api/bots/create-a-bot) to get started.

### Filter qualifiers for X Activity API subscriptions

We added an optional `filter.qualifiers` map to [X Activity API](/x-api/activity/introduction) subscriptions for event-specific filtering. Use `conversation_type` (`direct` or `group`) to scope `chat.received` events, or `direction` (`inbound` or `outbound`) for `follow.follow`, `follow.unfollow`, and `like.create` events. A subscription accepts up to 8 qualifiers, and unsupported keys or values return a 400 error.

### `is_subscriber` field in `broadcast.chat` events

`broadcast.chat` event payloads in the X Activity API now include an `is_subscriber` boolean alongside the message and author details, so you can tell whether the message came from a subscriber. See [event payloads](/x-api/activity/event-payloads) for the full payload.

### Legacy Pro plans moving to Pay-Per-Use

We are deprecating the legacy Pro plans (monthly and annual). After September 1, 2026, Pro subscribers are automatically migrated to Pay-Per-Use at the end of their current billing cycle. Migrated accounts default to a \$5,000 auto-recharge (triggered when the balance falls below \$250) and a \$10,000 per-cycle spend cap, and annual subscribers receive prorated credits instead of a card charge. You can adjust these settings in the Developer Portal. Learn more [here](https://devcommunity.x.com/t/important-update-legacy-x-api-pro-plans-are-moving-to-pay-per-use-ppu/273255).
</Update>

<Update label="Aug 13, 2026" description="X Ads API">
### Updated `video_total_views` definition

Expand Down