Automation rules
Automation rules
Automation on >x< refers to accounts or apps that take repeated actions without a person actively performing them. Understand what's allowed, what violates our rules, and how we detect and handle violations.
- Automation means repeated actions without a person actively performing them Account & Service Control
Updated April 2026
- Automation means repeated actions without a person actively performing them Account & Service Control
This page is primarily intended for developers.
- Automation means repeated actions without a person actively performing them Account & Service Control
For >x< users: You are ultimately responsible for the actions taken with your account, or by applications associated with your account. 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. If automated activity on your account violates the >x< Rules or these automation rules, >x< may take action on your account, including filtering your posts from search results or suspending your account.
- X users are responsible for automated activity on their accounts Account & Service Control
- Users should investigate a third-party application before authorizing it Account & Service Control
For more information on third-party applications, please see our article on connecting and revoking third-party applications.
- Users should investigate a third-party application before authorizing it Account & Service Control
- If you are a developer and have questions about these Automation Rules, please reach out here.
I. Ground Rules
Do!
- Build solutions that automatically broadcast helpful information in posts.
- Developers are encouraged to build automated posts, auto-replies and automated Direct Messages Account & Service Control
- Run creative campaigns that auto-reply to users who engage with your content.
- Developers are encouraged to build automated posts, auto-replies and automated Direct Messages Account & Service Control
- Build solutions that automatically respond to users in Direct Messages.
- Developers are encouraged to build automated posts, auto-replies and automated Direct Messages Account & Service Control
- Try new things that help people (and comply with our rules).
- Developers are encouraged to build automated posts, auto-replies and automated Direct Messages Account & Service Control
- Make sure your application provides a good user experience and performs well — and confirm that remains the case over time.
- Developers are encouraged to build automated posts, auto-replies and automated Direct Messages Account & Service Control
Don’t!
- Violate these or other policies. Be extra mindful of our rules about abuse and user privacy.
- Automation must not violate X's policies, with extra care on abuse and user privacy Legal Rights & Agreement Rules
- Abuse the >x< API or attempt to circumvent rate limits.
- The X API must not be abused and rate limits must not be circumvented Legal Rights & Agreement Rules
- 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.
- Non-API automation such as scripting the X website is prohibited and can lead to permanent suspension Account & Service Control
- Spam or bother users, or otherwise send them unsolicited messages.
- Users must not be spammed or sent unsolicited messages Legal Rights & Agreement Rules
A. The >x< Rules and the Developer Agreement and Policy
As with all activity on >x<, automated activity is subject to the >x< Rules and, if you’re a developer using the >x< API, the Developer Agreement and Policy.
- Automated activity is subject to the X Rules, and for API developers the Developer Agreement and Policy Legal Rights & Agreement Rules
You should carefully review these policies to ensure that your automated activity is compliant. 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.
- Automated activity is subject to the X Rules, and for API developers the Developer Agreement and Policy Legal Rights & Agreement Rules
- Violating these policies, or helping others violate them, can lead to enforcement and loss of API access Account & Service Control
Although all aspects of the >x< Rules and the Developer Agreement and Policy apply to automated activity, you should keep the following rules top of mind:
- Automated activity is subject to the X Rules, and for API developers the Developer Agreement and Policy Legal Rights & Agreement Rules
Spamming: You may not send automated posts or Direct Messages that are spam, or otherwise engage in spamming activity. Some examples of spammy behavior to avoid with automation include:
- Automated posts and Direct Messages must not be spam Legal Rights & Agreement Rules
- Trending topics: You may not automatically post about trending topics on >x<, or use automation to attempt to influence or manipulate trending topics.
- Automation must not post about trending topics or try to manipulate them Legal Rights & Agreement Rules
- Multiple posts/accounts: You may not post duplicative or substantially similar posts on one account or over multiple accounts you operate.
- Duplicative or substantially similar posts, and duplicate automated accounts, are not allowed Account & Service Control
- Duplicate accounts: You may not create and/or automate multiple accounts for duplicative or substantially similar use cases.
- Duplicative or substantially similar posts, and duplicate automated accounts, are not allowed Account & Service Control
- However, automating multiple accounts for related but non-duplicative use cases is permitted. For example, you may automate separate accounts to post when the Hubble Space Telescope passes over different cities, such as San Francisco or Hong Kong.
- Duplicative or substantially similar posts, and duplicate automated accounts, are not allowed Account & Service Control
Misleading links: You may not send automated posts or Direct Messages containing links that are misleading, including links that maliciously or deceptively redirect through landing pages or ad pages before displaying the final content.
- Automated posts and Direct Messages must not contain misleading links Legal Rights & Agreement Rules
Sensitive media: Automated posts and Direct Messages must comply with the >x< media policy, and you should mark your account as potentially sensitive if you intend to post graphic, pornographic, or potentially sensitive media.
- Automated posts and Direct Messages must follow the media policy, and sensitive-media accounts should be marked Content & IP Rights
Abusive behavior: You may not engage in any automated activity that encourages, promotes, or incites abuse, violence, hateful conduct, or harassment, on or off >x<.
- Automation must not encourage abuse, violence, hateful conduct or harassment, on or off X Legal Rights & Agreement Rules
Private information: You may not post private or confidential information about a person without their prior express authorization.
- Private or confidential information about a person must not be posted without their prior express authorization Data Access & Collection
B. Other Ground Rules for Automated Activity
In addition to the policies above, the following ground rules apply to all automated activity on >x<:
- Automated activity should not surprise or mislead users, or send mature content they did not ask for Legal Rights & Agreement Rules
- Don’t surprise or mislead users: Automated activity should honor users’ expectations. Ask for the user’s permission before taking an action if you aren’t sure.
- Automated activity should not surprise or mislead users, or send mature content they did not ask for Legal Rights & Agreement Rules
- Mature content or profanity: Don’t Direct Message, mention, or reply to users with potentially sensitive content (including profanity), unless they’ve clearly indicated an intent to receive it in advance.
- Automated activity should not surprise or mislead users, or send mature content they did not ask for Legal Rights & Agreement Rules
- Be thoughtful about the information you request or exchange on >x<
- Do not ask users for personal information in public posts; ask for the minimum in Direct Messages Data Access & Collection
- posts: Don’t ask users to send you personal or private information via a public post. If you need additional personal or private information from a user to provide them with customer service (or other similar use cases), you should ask the user to share such information by Direct Message or another private channel. You might even consider adding a Direct Message deep link to your post.
- Do not ask users for personal information in public posts; ask for the minimum in Direct Messages Data Access & Collection
- Direct Messages: You should only ask users for the minimum amount of information you need to provide them with service. If you need to request or exchange particularly sensitive information (such as credit card information), you should consider directing users to your website or other appropriate channel to do so.
- Do not ask users for personal information in public posts; ask for the minimum in Direct Messages Data Access & Collection
II. Activity-Specific Rules
The activity-specific rules in this section apply to taking specific automated actions on >x<. Please read these rules carefully, as they outline both permitted and prohibited use cases of automation.
- Violating the activity-specific rules, or helping others violate them, can lead to enforcement Account & Service Control
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. As a reminder, 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.
- Violating the activity-specific rules, or helping others violate them, can lead to enforcement Account & Service Control
A. Automated Actions Through Another User’s Account
x< users may authorize your app or service to access their >x< account through OAuth. 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.
- Authorizing an app through OAuth is not by itself enough consent for automated actions Account & Service Control
You may only take automated actions through another >x< user’s account if you:
- Automated actions through another user's account need a clear description, express consent and honored opt-outs Account & Service Control
- 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.
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.
- Substantially changing an app's purpose or functionality requires new express consent Account & Service Control
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.
- Consent rules cover every automated action through another account; bulk delete tools must warn posts are unrecoverable Account & Service Control
B. Automated posts
1. Posting automated posts
Automated posts that cross-post outside information: You may post automated posts based on sources of outside information — such as an RSS feed, weather data, etc. — as long as you are sufficiently authorized to publish such information.
- Automated posts may be based on outside information if the publisher is sufficiently authorized Content & IP Rights
Other automated posts (excluding mentions or replies): Provided you comply with all other rules, you may post automated posts for entertainment, informational, or novelty purposes. As a reminder, accounts posting duplicative, spammy, or otherwise prohibited content may be subject to suspension.
- Other automated posts are allowed for entertainment, informational or novelty purposes if all other rules are followed Account & Service Control
2. Posting automated mentions and replies
The reply and mention functions are intended to make communication between >x< users easier. Automating these actions to reach many users on an unsolicited basis is an abuse of the feature, and is not permitted. For example, sending automated replies to posts based on keyword searches alone is not permitted. Spammy or duplicative use of mentions and replies may result in enforcement action, such as the removal of your posts from Search or the suspension of your app or account.
- Automated replies and mentions that reach many users unsolicited are not permitted Legal Rights & Agreement Rules
However, you may send automated replies or mentions to >x< users so long as:
- Automated replies and mentions need opt-in, an opt-out, one per interaction and a reply to the original post Legal Rights & Agreement Rules
- in advance of sending the automated reply, the recipient or mentioned user(s) have requested or have clearly indicated an intent on >x< to be contacted by you (i.e. opted in), for example by replying to a post from your account, or by sending you a Direct Message;
- Automated replies and mentions need opt-in, an opt-out, one per interaction and a reply to the original post Legal Rights & Agreement Rules
- you provide a clear and easy way for such users to opt-out of receiving automated replies and mentions, and promptly honor all such opt-out requests;
- Automated replies and mentions need opt-in, an opt-out, one per interaction and a reply to the original post Legal Rights & Agreement Rules
- you only send one automated reply or mention per user interaction; and
- Automated replies and mentions need opt-in, an opt-out, one per interaction and a reply to the original post Legal Rights & Agreement Rules
- the automated reply or mention is a reply to the user’s original post (if your campaign is based on users posting a reply to your post).
- Automated replies and mentions need opt-in, an opt-out, one per interaction and a reply to the original post Legal Rights & Agreement Rules
Opt-in techniques and indications of user intent take many different forms, depending on the specifics of your use case and implementation. Some examples include:
- Opt-in can take many forms, but following an account alone is not enough Legal Rights & Agreement Rules
- A post from your account that clearly indicates that a user taking a specific action on that post (such as Reposting it) will opt the user into receiving an automated response.
- Opt-in can take many forms, but following an account alone is not enough Legal Rights & Agreement Rules
- A mention of your account by the user in a manner suggesting the user clearly wishes or intends to receive a response. If you want to run an auto-reply campaign with a campaign- or use-case-specific hashtag, users should also mention you in their posts.
- Opt-in can take many forms, but following an account alone is not enough Legal Rights & Agreement Rules
Note that a user following your account is not on its own a sufficient indication of user intent to receive an automated response.
- Opt-in can take many forms, but following an account alone is not enough Legal Rights & Agreement Rules
Additionally, we recommend that any accounts that will communicate with users via automated mentions or replies:
- X recommends filtering sensitive language and checking that the post still exists Legal Rights & Agreement Rules
- Appropriately filter responses based on potentially sensitive language in user handles, display names, and post text, as well as potentially sensitive media;
- X recommends filtering sensitive language and checking that the post still exists Legal Rights & Agreement Rules
- Check that the post you are mentioning or replying to still exists (for example, using the statuses/lookup endpoint on the >x< API).
- X recommends filtering sensitive language and checking that the post still exists Legal Rights & Agreement Rules
3. AI-Powered Automated Replies
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, as these can enhance user engagement, provide timely assistance, and foster innovative interactions on >x<. However, to safeguard user experience, prevent potential misuse, and ensure alignment with our rules, 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.
- AI-powered reply bots are allowed only with X's prior written and explicit approval Account & Service Control
C. Automated Direct Messages
Sending automated Direct Messages to users
You may not send unsolicited Direct Messages in a bulk or automated manner, and should be thoughtful about the frequency with which you contact users via Direct Message.
- Unsolicited Direct Messages must not be sent in a bulk or automated manner Legal Rights & Agreement Rules
You may send automated Direct Messages to users so long as:
- Automated Direct Messages are allowed only after the recipient opted in and with an easy opt-out Legal Rights & Agreement Rules
- in advance of sending the Direct Message, the recipient(s) have requested or have clearly indicated an intent on >x< to be contacted by you via Direct Message, for example by sending you a Direct Message; and
- Automated Direct Messages are allowed only after the recipient opted in and with an easy opt-out Legal Rights & Agreement Rules
- you provide a clear and easy way for such users to opt-out of receiving automated Direct Messages, and promptly honor all such opt-out requests.
- Automated Direct Messages are allowed only after the recipient opted in and with an easy opt-out Legal Rights & Agreement Rules
The fact that a user is technically able to receive a Direct Message from you (e.g. because the user follows you, has enabled the ability to receive Direct Messages from any account, or because the user is in a pre-existing Direct Message conversation with you) does not necessarily mean they have requested or expect to receive automated Direct Messages from you.
- Being able to receive a Direct Message does not by itself mean the user asked for automated ones Legal Rights & Agreement Rules
Interacting with users via Direct Message
Per the Ground Rules, remember to be thoughtful about the amount and type of information you request or exchange with users via Direct Messages. If you will be asking a user to provide personal or private information via an automated Direct Message, you must clearly explain how you will use the information you’re collecting. Consider including a link to your privacy policy in your Direct Message to the user, as well as in your >x< profile bio.
- Requesting personal information by automated Direct Message requires explaining how it will be used Data Access & Collection
Don’t publicly share information received in a Direct Message conversation with a user without first obtaining explicit consent from the user. For example, if a user asks you via Direct Message about a purchase they made from you, you may not mention the user in a public post that includes information about their purchase unless you have the user’s explicit consent to do so.
- Information received in a Direct Message must not be shared publicly without explicit consent Sharing & Disclosure
After a user-initiated interaction ends, don’t send additional follow-up Direct Messages or mention users in a post unless you get permission from the user.
- After a user-initiated interaction ends, no follow-up Direct Messages or mentions without permission Legal Rights & Agreement Rules
D. Automated actions you take on posts or accounts
Automated likes or hide replies: You may not like posts or hide replies in an automated manner.
- Automated likes and hiding replies are not allowed Legal Rights & Agreement Rules
Automated Reposts: Provided you comply with all other rules, you may Repost or Quote post in an automated manner for entertainment, informational, or novelty purposes. Automated Reposts often lead to negative user experiences, and bulk, aggressive, or spammy Reposting is a violation of the >x< Rules.
- Automated Reposts are allowed for stated purposes only; bulk or spammy Reposting violates the rules Legal Rights & Agreement Rules
Automated following/unfollowing: You may not follow or unfollow >x< accounts in a bulk, aggressive, or indiscriminate manner. Aggressive following is a violation of the >x< Rules. Please also review our following rules and best practices to ensure you are in compliance. Note that applications that claim to get users more followers are also prohibited under the >x< Rules.
- Following or unfollowing accounts in a bulk, aggressive or indiscriminate manner is not allowed Legal Rights & Agreement Rules
Automated adding to lists or collections: You may not add >x< users to lists or add posts to collections in a bulk or indiscriminate manner. Adding a large number of unrelated users to lists is a violation of the >x< Rules.
- Adding users to lists or posts to collections in a bulk or indiscriminate manner is not allowed Legal Rights & Agreement Rules