From 40f191863abc9802af26253fcf7eb012687cae2a Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Wed, 23 Sep 2026 13:11:31 +0000 Subject: [PATCH] docs: add changelog entry for OAuth token exchange broadcast scopes --- changelog.mdx | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/changelog.mdx b/changelog.mdx index 47c1347f0..2fbd5315c 100644 --- a/changelog.mdx +++ b/changelog.mdx @@ -7,6 +7,14 @@ 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). + + ### `broadcast` scopes added to OAuth 1.0a → OAuth 2.0 token exchange + + When you exchange an OAuth 1.0a user token for an OAuth 2.0 token, the granted scopes now include `broadcast.read` for **Read** permissions and `broadcast.write` for **Read and write** permissions. Existing users with these OAuth 1.0a permissions can call the broadcast endpoints under OAuth 2.0 without a new consent screen. + + See the [permission-to-scope mapping](/fundamentals/authentication/oauth-2-0/oauth-1-0a-token-exchange) on the OAuth 1.0a token exchange page. + + ### Migrate OAuth 1.0a user tokens to OAuth 2.0 with token exchange