X Activity API adds post.create and post.delete events

What this means for you

When an app posts for you on X, it often has to keep checking your profile to see if the post really went out. X now lets apps get a quick message the moment you post or delete something. That can make scheduling apps faster at confirming posts and spotting deleted ones. Nothing changes in how you post.

The details

• New events: post.create fires when the filtered user creates a post, including standalone posts, replies, quote posts and reposts. Inspect in_reply_to_tweet_id or referenced_tweets in the payload to tell them apart. post.delete fires when the filtered user deletes a post. Both filter on user_id.
• Public events: the X Activity API introduction lists both as public events, so they need no OAuth consent from the user being watched. Posts from protected accounts are not delivered, even with user-context authorization.
• Endpoints: create subscriptions with POST /2/activity/subscriptions, list, update and delete them under /2/activity/subscriptions, and receive events on the persistent stream GET /2/activity/stream or a registered webhook.
• Limits: up to 1,500 subscriptions on self-serve, 75,000 on Enterprise and 150,000 on Partner.
• Billing: the pricing page lists post.create at $0.005 per event and post.delete as not billed. The X Activity API introduction says each delivered Post event is billed as a Post, so check the Developer Console for what you are actually charged.
• Keyword use cases: the changelog says to keep using the Filtered Stream for keyword filtering and its full operator set.

What to do next

• Business owners: Nothing.
• Marketers and agencies: Nothing now. Tools may start confirming published or deleted X posts faster.
• Developers: Replace timeline polling for publish confirmation with post.create and post.delete subscriptions, and budget $0.005 per post.create event.