Publish (Go Live) or End a Broadcast

Deprecated. PUT /2/users/:user_id/broadcasts/:broadcast_id/state publishes a broadcast with state PUBLISH, or ends it with state END. Use POST /2/broadcasts to go live and PUT /2/broadcasts/:id/state to end; this route will be removed on January 1, 2027.

This route is deprecated and will be removed on January 1, 2027, after which it returns 404. To go live, use Go Live (POST /2/broadcasts), which creates and publishes a broadcast in one call. To end a broadcast, use End Broadcast (PUT /2/broadcasts/:id/state). See the migration guide.

Both actions use the same endpoint with different state values.

Endpoint: PUT /2/users/:user_id/broadcasts/:broadcast_id/state

Publish (state: “PUBLISH”)

Transitions NOT_STARTED → RUNNING. The broadcast becomes publicly visible on X. By default an announcement post is created. (Set should_not_tweet: true to suppress it.)

You can publish before your encoder connects: the response shows RUNNING right away, and video appears once the source is receiving it. Start your encoder before or right after publishing.

Request body

{
  "state": "PUBLISH",
  "title": "Live from the studio! Q&A time.",
  "should_not_tweet": false,
  "locale": "en",
  "chat_option": 2
}

Field	Type	Required	Description
state	string	Yes	Must be "PUBLISH".
title	string	No	Broadcast title / status text (also used for the announcement post if sent). Subject to X post length limits. If omitted, the broadcaster’s display name is used.
should_not_tweet	boolean	No	Set true to suppress the automatic announcement post. Default false (a post is sent). The strings "true" / "false" and 1 / 0 are also accepted.
locale	string	No	BCP 47 tag (e.g. "en", "en_US"). Affects discovery/recommendation.
chat_option	integer	No	Controls who can chat — see the values table below. A numeric string (e.g. "2") is also accepted. If omitted, the broadcast’s chat_option is 0 (no option set). Values outside 0–6 return 400.

Chat option values

chat_option is an integer enum controlling who can participate in chat:

Value	Meaning
0	None (no option set)
1	Chat disabled
2	Everyone
3	Verified accounts
4	Accounts the broadcaster follows
5	The broadcaster’s subscribers
6	Accounts the broadcaster follows and who they follow (2nd degree followers)

Set chat_option explicitly to choose who can chat.

Example request

curl -X PUT "https://api.x.com/2/users/172483972/broadcasts/2VNLjPpqaKWoep/state" \
  -H "Authorization: Bearer $USER_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"state":"PUBLISH","title":"Live from the studio! Q&A time.","chat_option":2}'

Response (on success)

{
  "broadcast": {
    ... full broadcast object with state: "RUNNING",
    "status": "Live from the studio! Q&A time.",
    "start_ms": "1772032035735",
    "language": "en",
    "chat_option": 2,
    ...
  }
}

• start_ms is set when it becomes live.
• The announcement post is created asynchronously. tweet_id is typically not present in this publish response — re-fetch the broadcast (GET .../broadcasts/:broadcast_id) a moment later to read tweet_id once the post exists.
• tweet_error: present, next to broadcast, only when the announcement post failed; it describes why. The broadcast still goes live.
• language is present only when you send locale.

End (state: “END”)

Transitions RUNNING → ENDED. Irreversible; you cannot restart a broadcast.

Request body (strict)

{
  "state": "END"
}

Do not include title, should_not_tweet, locale, or chat_option when ending. The server explicitly rejects them with 400 if any of these fields are present (for example, "title must not be set").

Ending a broadcast that isn’t running returns 400 with error_type: "badRequest".

Example request

curl -X PUT "https://api.x.com/2/users/172483972/broadcasts/2VNLjPpqaKWoep/state" \
  -H "Authorization: Bearer $USER_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"state":"END"}'

Response

{
  "success": true
}

After ending, stop your encoder. A replay may be available later if available_for_replay was true (or per platform policy).