X developer account announced that the Livestream API has been rebuilt from the ground up and is now open for immediate use. Third parties can use the same set of interfaces to start broadcasts, schedule events, manage chat operations, and handle real-time events related to alerts and overlays.

The official documentation divides capabilities into two core object categories. Stream Source is a reusable RTMP or RTMPS streaming point, created once and used for multiple broadcasts; Broadcast is a single live stream bound to that source, with states ranging from NOT_STARTED to RUNNING to ENDED. The standard process is to first create the source, then have the encoder stream, create the event, publish it online, and finally end it. The source must already be receiving streams for the interface to allow event creation.

The scheduling interface supports single and weekly recurring events, allowing for automatic start at a set time or manual publishing followed by online activation. Chat operates on two tracks: sending messages, deleting messages, and muting users go through the live broadcast interface, while real-time chat reading subscribes to the Activity API's broadcast.chat event, with a single subscription covering all events under that username without needing to re-subscribe for each event. Chat permissions can be set for all users, verified accounts, followed hosts, or subscribers, with a default bias towards verified accounts during publishing.

Access is not fully self-service. The documentation specifies that the Livestream API's scheduling endpoint is currently under the Enterprise plan, requiring a submission form that includes application number, existing package, product usage, and approximate monthly active users; clients with existing enterprise agreements can have their account manager enable access. The interface is hosted at api.x.com and accepts both OAuth 2.0 and OAuth 1.0a user contexts. Some old paths still carry user_id, while the new paths directly operate broadcasts, with old routes gradually being replaced.

This set of interfaces fills a long-standing gap in the developer community: feedback from public channels between 2025 and mid-2026 indicated an inability to programmatically read live chat or schedule events, with encoders only able to manually copy streaming addresses from Live Studio. By around July 2026, the platform had rolled out Live Studio to Premium users, and this update extends the command capabilities to third-party directors, overlays, and multi-platform distribution software.

The market mechanism allows the platform to transfer live production rights from the native interface to toolchains. Buyers include directing stations, multi-platform distributors, and media teams needing overlay comments, while sellers are X's enterprise packages and complete lifecycle interfaces subject to review thresholds. The event-driven aspect arises from competition with Twitch, YouTube, and Kick for creator tool layers. Beneficiaries are middleware that can integrate "one-click broadcasting to X" into their products, while those under pressure are integrators still relying on web scraping for chat or requiring hosts to manually copy keys; advertising and subscription revenue remains on X's playback page, with the API primarily targeting the broadcasting entry point.

Source: Public Information