Legal Rights & Agreement Rules · Restriction or exception
Automation must not violate X's policies, with extra care on abuse and user privacy
Under "Don't!", the first item tells developers not to violate "these or other policies" and to be extra mindful of the rules about abuse and user privacy. The page does not list which other policies it means here; later sections name the X Rules and the Developer Agreement and Policy.
Supporting quotations
Violate these or other policies. Be extra mindful of our rules about abuse and user privacy.
Qualifications & exceptions
Covers these automation rules and other policies; abuse and user privacy rules are singled out.
Not stated here
"Other policies" is not defined in this item, and the text of those policies is not supplied here.
Legal Rights & Agreement Rules · Restriction or exception
The X API must not be abused and rate limits must not be circumvented
Under "Don't!", the page tells developers not to abuse the X API or attempt to circumvent rate limits.
Supporting quotations
Abuse the >x< API or attempt to circumvent rate limits.
Not stated here
The page does not define what counts as abuse of the API or list the rate limits.
Legal Rights & Agreement Rules · Restriction or exception
Users must not be spammed or sent unsolicited messages
Under "Don't!", the page tells developers not to spam or bother users, or otherwise send them unsolicited messages. Later sections add specific opt-in conditions for automated replies, mentions and Direct Messages.
Supporting quotations
Spam or bother users, or otherwise send them unsolicited messages.
Qualifications & exceptions
Later sections set the conditions under which automated replies, mentions and Direct Messages may be sent.
Not stated here
The page does not define what makes a message "unsolicited" in this item.
Legal Rights & Agreement Rules · Restriction or exception
Automated activity is subject to the X Rules, and for API developers the Developer Agreement and Policy
As with all activity on X, automated activity is subject to the X Rules. A developer using the X API is also subject to the Developer Agreement and Policy. The page says all aspects of both apply to automated activity, and developers should review them to make sure their activity is compliant. It then lists rules to keep top of mind, which are additions to emphasize, not a replacement for those documents.
Supporting quotations
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.
You should carefully review these policies to ensure that your automated activity is compliant.
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:
Qualifications & exceptions
The Developer Agreement and Policy applies if you are a developer using the X API.
Not stated here
The text of the X Rules and the Developer Agreement and Policy is not supplied here, so this card cannot say what they require.
Legal Rights & Agreement Rules · Restriction or exception
Automated posts and Direct Messages must not be spam
The page prohibits sending automated posts or Direct Messages that are spam, or otherwise engaging in spamming activity. It lists examples of spammy behavior to avoid with automation; the examples are illustrative, not a complete list.
Supporting quotations
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:
Qualifications & exceptions
The listed examples are introduced as "some examples", so the list is not exhaustive.
Not stated here
The page does not define spam beyond the listed examples.
Legal Rights & Agreement Rules · Restriction or exception
Automation must not post about trending topics or try to manipulate them
As an example of spammy behavior, the page says a person may not automatically post about trending topics on X, or use automation to attempt to influence or manipulate trending topics.
Supporting quotations
Trending topics: You may not automatically post about trending topics on >x<, or use automation to attempt to influence or manipulate trending topics.
Legal Rights & Agreement Rules · Restriction or exception
Automated posts and Direct Messages must not contain misleading links
The page prohibits automated posts or Direct Messages that contain misleading links. It gives as examples links that maliciously or deceptively redirect through landing pages or ad pages before showing the final content.
Supporting quotations
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.
Qualifications & exceptions
Misleading links include, but are not limited to, malicious or deceptive redirects through landing or ad pages ("including").
Legal Rights & Agreement Rules · Restriction or exception
Automation must not encourage abuse, violence, hateful conduct or harassment, on or off X
The page prohibits any automated activity that encourages, promotes or incites abuse, violence, hateful conduct or harassment. The prohibition covers conduct both on and off X.
Supporting quotations
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<.
Qualifications & exceptions
Applies on or off X.
Legal Rights & Agreement Rules · Restriction or exception
Automated activity should not surprise or mislead users, or send mature content they did not ask for
The page says these ground rules apply to all automated activity on X. Automated activity should honor users' expectations, and the page says to ask for the user's permission before taking an action if unsure. It also says not to Direct Message, mention or reply to users with potentially sensitive content, including profanity, unless they have clearly indicated in advance an intent to receive it.
Supporting quotations
In addition to the policies above, the following ground rules apply to all automated activity on >x<:
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.
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.
Qualifications & exceptions
Applies to all automated activity on X.
Sensitive content may be sent only if the user clearly indicated an intent to receive it in advance.
Not stated here
The page does not say how a user's expectations are measured.
Legal Rights & Agreement Rules · Restriction or exception
Automated replies and mentions that reach many users unsolicited are not permitted
The page says the reply and mention functions are meant to make communication between X users easier. Automating them to reach many users on an unsolicited basis is called an abuse of the feature and is not permitted. For example, automated replies sent to posts based on keyword searches alone are not permitted. Spammy or duplicative use may result in enforcement action, such as removal of the person's posts from Search or suspension of their app or account. The next card sets the conditions under which automated replies or mentions are allowed.
Supporting quotations
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.
Qualifications & exceptions
Applies to automated replies and mentions sent on an unsolicited basis to many users.
Enforcement is stated as "may"; removal from Search and suspension are examples.
Not stated here
The page does not say how many users counts as "many".
Legal Rights & Agreement Rules · Restriction or exception
Automated replies and mentions need opt-in, an opt-out, one per interaction and a reply to the original post
A person may send automated replies or mentions to X users only so long as four conditions are met. First, before sending, the recipient or mentioned users have requested or clearly indicated on X an intent to be contacted by the sender (opted in), for example by replying to a post from the account or sending a Direct Message. Second, the sender provides a clear and easy way to opt out and promptly honors all opt-out requests. Third, the sender sends only one automated reply or mention per user interaction. Fourth, where the campaign is based on users replying to the sender's post, the automated reply is a reply to the user's original post.
Supporting quotations
However, you may send automated replies or mentions to >x< users so long as:
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;
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;
you only send one automated reply or mention per user interaction; and
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).
Qualifications & exceptions
All four conditions are required (the list is joined by "and").
The fourth condition applies only if the campaign is based on users posting a reply to the sender's post.
Not stated here
The page does not define "user interaction" for the one-reply limit beyond the examples given.
Legal Rights & Agreement Rules · Restriction or exception
Opt-in can take many forms, but following an account alone is not enough
The page says opt-in techniques and indications of user intent take many forms depending on the use case. Examples are a post from the account that clearly says a specific action, such as Reposting it, will opt the user into an automated response, and a user's mention of the account suggesting they wish to receive a response. If a campaign uses a hashtag, users should also mention the account in their posts. The page states that a user following an account is not on its own a sufficient indication of intent to receive an automated response.
Supporting quotations
Opt-in techniques and indications of user intent take many different forms, depending on the specifics of your use case and implementation.
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.
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.
Note that a user following your account is not on its own a sufficient indication of user intent to receive an automated response.
Qualifications & exceptions
The examples are illustrative ("some examples").
For a campaign using a campaign- or use-case-specific hashtag, users should also mention the account in their posts.
Following is not sufficient on its own.
Not stated here
The page does not list every acceptable way to opt in.
Legal Rights & Agreement Rules · Procedure
X recommends filtering sensitive language and checking that the post still exists
The page recommends that accounts communicating with users through automated mentions or replies appropriately filter responses based on potentially sensitive language in user handles, display names and post text, and on potentially sensitive media. It also recommends checking that the post being mentioned or replied to still exists, for example using the statuses/lookup endpoint on the X API. These are recommendations, not stated requirements.
Supporting quotations
Additionally, we recommend that any accounts that will communicate with users via automated mentions or replies:
Appropriately filter responses based on potentially sensitive language in user handles, display names, and post text, as well as potentially sensitive media;
Check that the post you are mentioning or replying to still exists (for example, using the statuses/lookup endpoint on the >x< API).
Qualifications & exceptions
Stated as "we recommend", not as a requirement.
Applies to accounts that communicate with users via automated mentions or replies.
Legal Rights & Agreement Rules · Restriction or exception
Unsolicited Direct Messages must not be sent in a bulk or automated manner
The page says a person may not send unsolicited Direct Messages in a bulk or automated manner, and should be thoughtful about how often they contact users by Direct Message. The next card sets the conditions under which automated Direct Messages are allowed.
Supporting quotations
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.
Qualifications & exceptions
The prohibition applies to unsolicited Direct Messages sent in a bulk or automated manner.
Frequency is a "should be thoughtful" recommendation, not a stated limit.
Not stated here
The page does not give a number for acceptable Direct Message frequency.
Legal Rights & Agreement Rules · Restriction or exception
Automated Direct Messages are allowed only after the recipient opted in and with an easy opt-out
A person may send automated Direct Messages to users only so long as two conditions are met. First, before sending, the recipient has requested or clearly indicated on X an intent to be contacted by the sender via Direct Message, for example by sending the sender a Direct Message. Second, the sender provides a clear and easy way to opt out of automated Direct Messages and promptly honors all opt-out requests. Both conditions are required.
Supporting quotations
You may send automated Direct Messages to users so long as:
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
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.
Qualifications & exceptions
Both conditions are required (the list is joined by "and").
The opt-in must come before the Direct Message is sent and must be for contact by Direct Message.
Not stated here
The page does not list every way a user can indicate intent beyond the example given.
Legal Rights & Agreement Rules · Restriction or exception
Being able to receive a Direct Message does not by itself mean the user asked for automated ones
The page says that a user being technically able to receive a Direct Message from the sender does not necessarily mean the user has requested or expects automated Direct Messages from the sender. It gives three examples of technical ability: the user follows the sender, the user has enabled receiving Direct Messages from any account, or the user is in an existing Direct Message conversation with the sender.
Supporting quotations
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.
Qualifications & exceptions
The wording is "does not necessarily mean", so ability to receive does not settle the question either way.
The three situations are examples ("e.g.").
Legal Rights & Agreement Rules · Restriction or exception
After a user-initiated interaction ends, no follow-up Direct Messages or mentions without permission
The page says that after a user-initiated interaction ends, a person may not send additional follow-up Direct Messages or mention users in a post unless they get permission from the user.
Supporting quotations
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.
Qualifications & exceptions
Applies after a user-initiated interaction ends.
Permission from the user is the exception.
Not stated here
The page does not say when an interaction is considered to have ended.
Legal Rights & Agreement Rules · Restriction or exception
Automated likes and hiding replies are not allowed
The page says a person may not like posts or hide replies in an automated manner.
Supporting quotations
Automated likes or hide replies: You may not like posts or hide replies in an automated manner.
Legal Rights & Agreement Rules · Permission or license
Automated Reposts are allowed for stated purposes only; bulk or spammy Reposting violates the rules
Provided all other rules are followed, the page says a person may Repost or Quote post in an automated manner for entertainment, informational or novelty purposes. It says automated Reposts often lead to negative user experiences, and that bulk, aggressive or spammy Reposting is a violation of the X Rules.
Supporting quotations
Provided you comply with all other rules, you may Repost or Quote post in an automated manner for entertainment, informational, or novelty purposes.
bulk, aggressive, or spammy Reposting is a violation of the >x< Rules.
Qualifications & exceptions
Allowed only for entertainment, informational or novelty purposes and only if all other rules are followed.
Bulk, aggressive or spammy Reposting is a violation.
Not stated here
The page does not define bulk or aggressive Reposting.
The linked X Rules text is not supplied here, so this card cannot say what they require.
Legal Rights & Agreement Rules · Restriction or exception
Following or unfollowing accounts in a bulk, aggressive or indiscriminate manner is not allowed
The page says a person may not follow or unfollow X accounts in a bulk, aggressive or indiscriminate manner, and that aggressive following violates the X Rules. It points readers to following rules and best practices, which are linked but not supplied here. It also says applications that claim to get users more followers are prohibited under the X Rules.
Supporting quotations
You may not follow or unfollow >x< accounts in a bulk, aggressive, or indiscriminate manner.
applications that claim to get users more followers are also prohibited under the >x< Rules.
Qualifications & exceptions
The prohibition applies to bulk, aggressive or indiscriminate following or unfollowing.
Applications that claim to get users more followers are separately prohibited.
Not stated here
The linked following rules and best practices are not supplied here, so this card cannot say what they require.
Legal Rights & Agreement Rules · Restriction or exception
Adding users to lists or posts to collections in a bulk or indiscriminate manner is not allowed
The page says a person may not add X users to lists or add posts to collections in a bulk or indiscriminate manner, and that adding a large number of unrelated users to lists violates the X Rules.
Supporting quotations
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.
Qualifications & exceptions
The prohibition applies to bulk or indiscriminate additions.
Not stated here
The page does not say how many additions count as a large number.
The linked X Rules text is not supplied here, so this card cannot say what they require.