Automate Twitter
HumDay reads Twitter’s own published API description and derives 80 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.
What Twitter is
Twitter API v2 available endpoints
API host: api.twitter.com
What HumDay can do in Twitter
29 documented operations change something in Twitter.
- POSTCreate a new DM Conversation
/2/dm_conversations - POSTSend a new message to a DM Conversation
/2/dm_conversations/{dm_conversation_id}/messages - POSTSend a new message to a user
/2/dm_conversations/with/{participant_id}/messages - POSTCreate List
/2/lists - POSTCauses the User (in the path) to like the specified Tweet
/2/users/{id}/likes - POSTMute User by User ID.
/2/users/{id}/muting - POSTAdd a List member
/2/lists/{id}/members - POSTBlock User by User ID
/2/users/{id}/blocking - POSTCauses the User (in the path) to retweet the specified Tweet.
/2/users/{id}/retweets - POSTAdd Tweet to Bookmarks
/2/users/{id}/bookmarks - POSTFollow User
/2/users/{id}/following - POSTPin a List
/2/users/{id}/pinned_lists - POSTFollow a List
/2/users/{id}/followed_lists - POSTAdd/Delete rules
/2/tweets/search/stream/rules - POSTCreate compliance job
/2/compliance/jobs - DELETEDelete List
/2/lists/{id} - PUTUpdate List.
/2/lists/{id} - DELETECauses the User (in the path) to unlike the specified Tweet
/2/users/{id}/likes/{tweet_id} - DELETEUnpin a List
/2/users/{id}/pinned_lists/{list_id} - DELETEUnfollow a List
/2/users/{id}/followed_lists/{list_id} - POSTCreation of a Tweet
/2/tweets - DELETECauses the User (in the path) to unretweet the specified Tweet
/2/users/{id}/retweets/{source_tweet_id} - DELETEUnmute User by User ID
/2/users/{source_user_id}/muting/{target_user_id} - DELETEUnblock User by User ID
/2/users/{source_user_id}/blocking/{target_user_id} - DELETEUnfollow User
/2/users/{source_user_id}/following/{target_user_id} - DELETETweet delete by Tweet ID
/2/tweets/{id} - DELETERemove a List member
/2/lists/{id}/members/{user_id} - DELETERemove a bookmarked Tweet
/2/users/{id}/bookmarks/{tweet_id} - PUTHide replies
/2/tweets/{tweet_id}/hidden
What HumDay can read from Twitter
These are the operations a schedule or a trigger can watch.
- GETUser lookup by IDs
/2/users - GETGet recent DM Events
/2/dm_events - GETReturns User objects that are members of a List by the provided List ID.
/2/lists/{id}/members - GETRetrieve the list of Users who purchased a ticket to the given space
/2/spaces/{id}/buyers - GETReturns User objects that follow a List by the provided List ID
/2/lists/{id}/followers - GETGet a User's List Memberships
/2/users/{id}/list_memberships - GETUser lookup by usernames
/2/users/by - GETUser lookup me
/2/users/me - GETUser lookup by ID
/2/users/{id} - GETReturns User objects that are muted by the provided User ID
/2/users/{id}/muting - GETUser Tweets timeline by User ID
/2/users/{id}/tweets - GETReturns User objects that are blocked by provided User ID
/2/users/{id}/blocking - GETUser mention timeline by User ID
/2/users/{id}/mentions - GETBookmarks by User
/2/users/{id}/bookmarks - GETFollowers by User ID
/2/users/{id}/followers - GETFollowing by User ID
/2/users/{id}/following - GETGet a User's Owned Lists.
/2/users/{id}/owned_lists - GETReturns Tweet objects liked by the provided User ID
/2/users/{id}/liked_tweets - GETGet a User's Pinned Lists
/2/users/{id}/pinned_lists - GETReturns User objects that have liked the provided Tweet ID
/2/tweets/{id}/liking_users - GETReturns User objects that have retweeted the provided Tweet ID
/2/tweets/{id}/retweeted_by - GETGet User's Followed Lists
/2/users/{id}/followed_lists - GETGet DM Events for a DM Conversation
/2/dm_conversations/{id}/dm_events - GETReturns the OpenAPI Specification document.
/2/openapi.json - GETSearch for Spaces
/2/spaces/search - GETList Compliance Jobs
/2/compliance/jobs - GETUser lookup by username
/2/users/by/username/{username} - GETList lookup by List ID.
/2/lists/{id} - GETFull archive search counts
/2/tweets/counts/all - GETFull-archive search
/2/tweets/search/all - GETUser home timeline by User ID
/2/users/{id}/timelines/reverse_chronological - GETRecent search counts
/2/tweets/counts/recent - GETRecent search
/2/tweets/search/recent - GETFiltered stream
/2/tweets/search/stream - GETGet DM Events for a DM Conversation
/2/dm_conversations/with/{participant_id}/dm_events - GETUsers Compliance stream
/2/users/compliance/stream - GETSpace lookup up Space IDs
/2/spaces - GETTweet lookup by Tweet IDs
/2/tweets - GETList Tweets timeline by List ID.
/2/lists/{id}/tweets - GETRules lookup
/2/tweets/search/stream/rules - GETSpace lookup by Space ID
/2/spaces/{id} - GETTweet lookup by Tweet ID
/2/tweets/{id} - GETTweets Label stream
/2/tweets/label/stream - GETSample stream
/2/tweets/sample/stream - GETSpace lookup by their creators
/2/spaces/by/creator_ids - GETFirehose stream
/2/tweets/firehose/stream - GETSample 10% stream
/2/tweets/sample10/stream - GETTweets Compliance stream
/2/tweets/compliance/stream - GETRetrieve Tweets from a Space.
/2/spaces/{id}/tweets - GETGet Compliance Job
/2/compliance/jobs/{id} - GETRetrieve Tweets that quote a Tweet.
/2/tweets/{id}/quote_tweets
How automating Twitter works
- Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
- Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
- See it proven. The program runs and shows you the result before it is allowed near your live Twitter account.
- Grant access, then go live. You approve the specific Twitter operations it may use — and only those.
Popular Twitter integrations
Connect Twitter to the tools people pair it with most.
- Twitter and OData for namespace microsoft.graphintegration
- Twitter and Cloudflareintegration
- Twitter and NetBoxintegration
- Twitter and GitHubintegration
- Twitter and Mistintegration
- Twitter and Loket.nlintegration
- Twitter and Atlassian The Jira Cloud platformintegration
- Twitter and Magento B2Bintegration
- Twitter and Stripeintegration
- Twitter and Zuora Reference Billingintegration
- Twitter and bunqintegration
- Twitter and DocuSignintegration
Automate Twitter with these
- Discord242 operations
- CPY PeerTube185 operations
- Mastodon Specification (https //github.com/mastodon/mastodon)127 operations
- spoonacular99 operations
- Discourse Documentation84 operations
- Trashnothing trash nothing76 operations
- Contribly44 operations
- Clubhouseapi Clubhouse41 operations
- Semantria41 operations
- DEV Forem40 operations
- Medium32 operations
- Instagram24 operations
Categories
Questions about Twitter automation
- Can HumDay connect to Twitter?
- Yes. HumDay reads Twitter's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 80 operations are documented.
- Do I need to write code to automate Twitter?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Twitter account.
- What can HumDay do in Twitter?
- 29 of the 80 documented operations change something in Twitter, and 51 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my Twitter account safe?
- Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Twitter is held behind that approval.
Where this came from
The operations above are read from a published API description for Twitter at api.twitter.com/2/openapi.json. Descriptions are the provider’s own words, not ours. Last published 2023-02-17.