Automation means repeated actions without a person actively performing them
The page defines automation on X as accounts or apps that take repeated actions without a person actively performing them. It says the page explains what is allowed, what violates the rules, and how violations are detected and handled. It is labelled "Updated April 2026" and is primarily intended for developers, so much of it addresses people building apps or bots rather than people who only use X.
Supporting quotations
Automation on >x< refers to accounts or apps that take repeated actions without a person actively performing them.
Updated April 2026
This page is primarily intended for developers.
Qualifications & exceptions
The page says it is primarily intended for developers.
The page is labelled as updated April 2026; no effective date is stated.
Not stated here
The page does not say how many repeated actions, or how often, make an account or app count as automated.
Account & Service Control · Company practice
X users are responsible for automated activity on their accounts
A user is ultimately responsible for actions taken with their account and for actions by applications associated with their account. If automated activity on the account violates the X Rules or these automation rules, X may take action on the account. The page names two examples: filtering the account's posts from search results, or suspending the account. The wording is "may", so these are possible responses, and the page does not say when each applies.
Supporting quotations
You are ultimately responsible for the actions taken with your account, or by applications associated with your account.
Users should investigate a third-party application before authorizing it
Before a user authorizes a third-party application to access or use their account, the page tells the user to make sure they have thoroughly investigated the application and understand what it will do. The page also points to a separate article on connecting and revoking third-party applications; that article is not part of this document and its text was not supplied.
Supporting quotations
Before authorizing a third-party application to access or use your account, make sure you've thoroughly investigated the application and understand what it will do.
Developers are encouraged to build automated posts, auto-replies and automated Direct Messages
Under "Do!", the page encourages building solutions that automatically broadcast helpful information in posts, run auto-reply campaigns to users who engage with the account's content, and automatically respond to users in Direct Messages. It also says to try new things that help people, as long as they comply with the rules, and to make sure the application gives a good user experience and keeps performing well over time. These are encouragements, not permissions that override the later rules on replies and Direct Messages.
Supporting quotations
Build solutions that automatically broadcast helpful information in posts.
Run creative campaigns that auto-reply to users who engage with your content.
Build solutions that automatically respond to users in Direct Messages.
Try new things that help people (and comply with our rules).
Make sure your application provides a good user experience and performs well — and confirm that remains the case over time.
Qualifications & exceptions
The page says new things must comply with X's rules.
Later sections set opt-in and opt-out conditions for automated replies, mentions and Direct Messages.
Not stated here
The page does not say how X checks that an application keeps a good user experience over time.
Account & Service Control · Restriction or exception
Non-API automation such as scripting the X website is prohibited and can lead to permanent suspension
The page tells developers not to use non-API-based forms of automation, with scripting the X website as the example. It says using these techniques may result in the permanent suspension of the account. The permitted route for automation is therefore the X API, subject to the other rules on this page.
Supporting quotations
Use non-API-based forms of automation, such as scripting the >x< website. The use of these techniques may result in the permanent suspension of your account.
Qualifications & exceptions
The suspension consequence is stated as "may", so it is possible, not automatic.
Scripting the X website is an example ("such as"); other non-API methods are also covered.
Not stated here
The page does not say which other techniques count as non-API-based automation.
Account & Service Control · Company practice
Violating these policies, or helping others violate them, can lead to enforcement and loss of API access
Automated applications or activities that violate these policies, or that facilitate or induce users to violate them, may be subject to enforcement action, potentially including suspension of associated X accounts. X may also rate limit, suspend or terminate a developer's access to the X API based on violations of these policies. The wording is "may" and "potentially", so these are possible responses, and the page does not say which violation leads to which response.
Supporting quotations
Automated applications or activities that violate these policies, or that facilitate or induce users to violate them, may be subject to enforcement action, potentially including suspension of associated >x< accounts. We may also rate limit, suspend, or terminate developers’ access to the >x< API based on violations of these policies.
Qualifications & exceptions
Applies to violations of these policies, and to activity that facilitates or induces users to violate them.
Enforcement is stated as "may" and "potentially including".
Not stated here
The page does not describe a notice or appeal process for enforcement action.
Account & Service Control · Restriction or exception
Duplicative or substantially similar posts, and duplicate automated accounts, are not allowed
The page says a person may not post duplicative or substantially similar posts on one account or across multiple accounts they operate. It also says a person may not create or automate multiple accounts for duplicative or substantially similar use cases. An exception follows: automating multiple accounts for related but non-duplicative use cases is permitted. The page's example is separate accounts that post when the Hubble Space Telescope passes over different cities.
Supporting quotations
You may not post duplicative or substantially similar posts on one account or over multiple accounts you operate.
You may not create and/or automate multiple accounts for duplicative or substantially similar use cases.
However, automating multiple accounts for related but non-duplicative use cases is permitted.
Qualifications & exceptions
Multiple accounts are permitted only for related but non-duplicative use cases.
The Hubble example is an illustration of a permitted use, not a limit.
Not stated here
The page does not say how different two use cases must be to count as non-duplicative.
Account & Service Control · Company practice
Violating the activity-specific rules, or helping others violate them, can lead to enforcement
The activity-specific rules apply to taking specific automated actions on X, and the page says to read them carefully because they describe both permitted and prohibited uses of automation. Automated applications or activities that violate these rules, or that facilitate or induce users to violate them, may be subject to enforcement action, including suspension of associated X accounts. X may also rate limit, suspend or terminate developers' access to the X API based on violations of these rules. The page reminds readers to review the spam guidelines in the X Rules so that activity by them, their app, or other users through their app or service is not flagged as spam.
Supporting quotations
The activity-specific rules in this section apply to taking specific automated actions on >x<.
Automated applications or activities that violate these rules, or that facilitate or induce users to violate them, may be subject to enforcement action, including suspension of associated >x< accounts. We may also rate limit, suspend, or terminate developers’ access the >x< API based on violations of these rules.
you should also carefully review the spam guidelines in the >x< Rules to avoid having activities performed by you, your app, or other users through your app or service flagged as spam.
Qualifications & exceptions
Applies to violations of the activity-specific rules and to activity that facilitates or induces users to violate them.
Enforcement is stated as "may".
Not stated here
The spam guidelines in the X Rules are linked but their text is not supplied here.
The page does not say which violation leads to which response.
Account & Service Control · Restriction or exception
Authorizing an app through OAuth is not by itself enough consent for automated actions
Users may authorize an app or service to access their X account through OAuth. The page says that this authorization does not by itself constitute sufficient consent to take automated actions through that user's account. The consent conditions in the next card apply as well.
Supporting quotations
A user authorizing your app or service to access their >x< account through OAuth does not by itself constitute sufficient consent to take automated actions through that user’s account.
Qualifications & exceptions
Applies to automated actions taken through a user's account by an app or service the user has authorized through OAuth.
Account & Service Control · Restriction or exception
Automated actions through another user's account need a clear description, express consent and honored opt-outs
A person may take automated actions through another X user's account only if they do all three things: clearly describe to the user the types of automated actions that will occur, receive the user's express consent to take them, and immediately honor a user's request to opt out of further automated actions. The three items are joined by "and", so all are required.
Supporting quotations
You may only take automated actions through another >x< user’s account if you:
clearly describe to the user the types of automated actions that will occur;
receive express consent from the user to take those automated actions; and
immediately honor a user’s request to opt-out of further automated actions.
Qualifications & exceptions
All three conditions are required (the list is joined by "and").
Applies to automated actions through another X user's account.
Not stated here
The page does not say how express consent must be collected or recorded.
Account & Service Control · Restriction or exception
Substantially changing an app's purpose or functionality requires new express consent
If a person substantially changes the purpose or functionality of their app or service, the page says they must re-obtain express consent from the user to take automated action through the user's account before doing so.
Supporting quotations
If you substantially change the purpose or functionality of your app or service, you must re-obtain express consent from the user to take automated action through their account before doing so.
Qualifications & exceptions
Applies if the purpose or functionality is substantially changed.
The new consent must be obtained before the automated action.
Not stated here
The page does not say what counts as a substantial change.
Account & Service Control · Restriction or exception
Consent rules cover every automated action through another account; bulk delete tools must warn posts are unrecoverable
The consent requirements apply to any automated action through another X user's account, with posting, sending Direct Messages, deleting posts or Direct Messages, and following or unfollowing named as examples. For applications that let users delete posts in a bulk or automated manner, the page also says the application must clearly state that posts are not recoverable once deleted.
Supporting quotations
These requirements apply to any automated action taken through another >x< user’s account, including posting posts, sending Direct Messages, deleting posts or Direct Messages, or following/unfollowing other accounts.
For applications that offer users the ability to delete posts in a bulk or automated manner, you must also clearly state that posts are not recoverable once deleted.
Qualifications & exceptions
The listed actions are examples ("including").
The warning duty applies to applications that offer deletion of posts in a bulk or automated manner.
Account & Service Control · Permission or license
Other automated posts are allowed for entertainment, informational or novelty purposes if all other rules are followed
Excluding mentions and replies, the page says a person may post automated posts for entertainment, informational or novelty purposes, provided they comply with all other rules. It reminds readers that accounts posting duplicative, spammy or otherwise prohibited content may be suspended.
Supporting quotations
Provided you comply with all other rules, you may post automated posts for entertainment, informational, or novelty purposes.
accounts posting duplicative, spammy, or otherwise prohibited content may be subject to suspension.
Qualifications & exceptions
Does not cover automated mentions or replies, which have their own rules.
Allowed only for entertainment, informational or novelty purposes and only if all other rules are followed.
Suspension is stated as "may".
Account & Service Control · Restriction or exception
AI-powered reply bots are allowed only with X's prior written and explicit approval
Provided all other rules are followed, the page says a person may use artificial intelligence to create automated reply bots that generate dynamic, context-aware responses. The deployment or operation of any AI reply bot, however, requires prior written and explicit approval from X. The page says to contact a dedicated point of contact or submit a request through the developer portal for review.
Supporting quotations
Provided you comply with all other rules, you may leverage artificial intelligence (AI) technologies to create automated reply bots that generate dynamic, context-aware responses
the deployment or operation of any AI reply bot requires prior written and explicit approval from >x<. Contact your dedicated point of contact or submit a request through the developer portal for review.
Qualifications & exceptions
Applies to the deployment or operation of any AI reply bot.
The approval must be prior, written and explicit.
AI reply bots must also comply with all other rules.
Not stated here
The page does not say what X considers when reviewing an approval request, or how long review takes.