Skip to content
Open
Changes from all commits
Commits
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
10 changes: 3 additions & 7 deletions changelog.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -7,15 +7,11 @@ 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="Nov 10, 2026" description="X API">
### Read-only mode for the X MCP and X Ads MCP

You can now make an MCP connection read-only by adding `?read_only=true` to the server URL: `https://api.x.com/mcp?read_only=true` or `https://ads-api.x.com/mcp?read_only=true`. A read-only connection offers only the tools that read data. Tools that post, send messages, or create, change, or delete anything are left out of the tool list and refused by the server, even if your token has write scopes. Connections without the parameter are unchanged.

See [Read-only mode](/tools/mcp#read-only-mode) for the accepted spellings and a config example.
<Update label="Nov 16, 2026" description="X API">
No new product updates this week.
</Update>

<Update label="Nov 5, 2026" description="X API v2">
<Update label="Nov 10, 2026" description="X API">
### Livestream API: new `/2/sources` and `/2/broadcasts` routes; `/2/users/:user_id` routes deprecated

You can now take a stream source live in one call with [`POST /2/broadcasts`](/livestream-api/broadcasts/go-live). It creates and publishes the broadcast together and returns it already `RUNNING` (`201`), or returns the source's live broadcast unchanged with `200` if there already is one, so it's safe to retry. Broadcasts are ended with [`PUT /2/broadcasts/:id/state`](/livestream-api/broadcasts/end-broadcast), deleted with [`DELETE /2/broadcasts/:id`](/livestream-api/broadcasts/delete-broadcast-by-id), and read with [`GET /2/broadcasts`](/livestream-api/broadcasts/get-broadcasts) and [`GET /2/broadcasts/:id`](/livestream-api/broadcasts/get-broadcast-by-id).
Expand Down