Twitter API v2
Browse all Twitter APIs✓ Official Vendor SpecSocial MediaSocial Publishingbearer, oauth2109 EndpointsREST
For Agents
Post tweets, search conversations, stream real-time content, and manage user interactions on Twitter. Supports 109 endpoints covering tweets, DMs, lists, communities, and Spaces.
Use for: I need to post a tweet with an image attachment, Search for recent tweets mentioning a specific brand, I want to set up a real-time stream for tweets matching specific keywords, Retrieve the follower list for a given Twitter user
Not supported: Does not handle ad campaigns, analytics dashboards, or audience insights — use for tweet content, user data, and messaging only.
Access and interact with posts, users, direct messages, communities, lists, and Spaces on the Twitter platform through 109 endpoints. Supports full-text search across historical and recent tweets, real-time filtered streams, and compliance data feeds. Provides community management, user relationship lookups, and engagement actions including likes and bookmarks.
Install Jentic One Beta
Connect the Twitter API v2 to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Twitter API v2, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Twitter API v2 API.
Search historical and recent tweets by keyword, hashtag, or user mention with boolean operators
Stream real-time tweets matching filter rules via persistent HTTP connections
Send and retrieve direct messages across conversations with specific participants
Look up user profiles, followers, and following relationships by ID or username
Create, delete, and quote tweets with media attachments and polls
Browse and search Twitter Communities and their member posts
Retrieve trending topics by geographic location (WOEID)
Use Cases
Patterns agents use Twitter API v2 API for, with concrete tasks.
★ AI Agent Social Monitoring
An AI agent searches for tweets mentioning a brand or topic using the /2/tweets/search/recent endpoint, analyzes sentiment and volume, and triggers alerts when engagement spikes. Through Jentic, the agent discovers the search endpoint by intent, loads the query schema, and executes searches without manual API setup. Handles up to 450 requests per 15-minute window on the standard tier.
Search for tweets mentioning '@acme' posted in the last 24 hours using /2/tweets/search/recent and return the 10 most engaged results sorted by retweet count
Real-Time Content Streaming
Filter and receive tweets in real time matching specific rules — keywords, user handles, geographic locations, or conversation threads. The /2/tweets/search/stream endpoint delivers a persistent HTTP stream of matching tweets within seconds of posting. Supports up to 25 concurrent rules on the basic access level and 1,000 rules on academic research access.
Add a filter rule for tweets containing 'artificial intelligence' with language:en to /2/tweets/search/stream/rules and open the stream connection
Community Engagement Analysis
Retrieve posts, members, and metadata from Twitter Communities using /2/communities/{id} and /2/communities/search. Analyze engagement patterns within niche communities to identify influential voices and trending discussion topics. Supports pagination through community member lists and post timelines.
Search for Twitter Communities matching 'machine learning' via /2/communities/search and retrieve the top community's member count and recent posts
Automated Direct Messaging
Send direct messages to users, retrieve conversation histories, and monitor DM events through the /2/dm_conversations endpoints. Supports creating new conversations, sending messages to existing threads, and listing DM events with pagination. Enables customer support bots and notification workflows that communicate privately with users.
Send a direct message 'Your order has shipped!' to participant_id 12345 via POST /2/dm_conversations/with/{participant_id}/messages
Tweet Publishing and Thread Creation
Publish tweets, create multi-tweet threads, and attach media including images, videos, and polls via POST /2/tweets. Supports reply threading by setting in_reply_to_tweet_id, quote tweets, and scheduled content workflows. Media uploads use the /2/media/upload endpoint with chunked transfer for large files.
Create a tweet thread by posting an initial tweet via POST /2/tweets and replying to it with a second tweet using in_reply_to_tweet_id
Key Endpoints
109 endpoints — access and interact with posts, users, direct messages, communities, lists, and spaces on the twitter platform through 109 endpoints.
METHOD
PATH
DESCRIPTION
POST
/2/tweets
Create a new tweet
GET
/2/tweets/search/recent
Search recent tweets (last 7 days)
GET
/2/tweets/search/all
Full-archive tweet search
GET
/2/tweets/search/stream
Real-time filtered tweet stream
GET
/2/users/{id}
Look up a user by ID
POST
/2/dm_conversations/with/{participant_id}/messages
Send a direct message
GET
/2/communities/search
Search Twitter Communities
GET
/2/trends/by/woeid/{woeid}
Get trending topics by location
POST
/2/tweets
Create a new tweet
GET
/2/tweets/search/recent
Search recent tweets (last 7 days)
GET
/2/tweets/search/all
Full-archive tweet search
GET
/2/tweets/search/stream
Real-time filtered tweet stream
GET
/2/users/{id}
Look up a user by ID
POST
/2/dm_conversations/with/{participant_id}/messages
Send a direct message
GET
/2/communities/search
Search Twitter Communities
GET
/2/trends/by/woeid/{woeid}
Get trending topics by location
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Twitter OAuth 2.0 tokens and Bearer keys are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens with only the required permissions (tweet.read, tweet.write, dm.read) — raw API keys and client secrets never enter the agent's context.
Intent-based discovery
Agents search by intent (e.g., 'search recent tweets about a brand') and Jentic returns the matching /2/tweets/search/recent operation with its full query parameter schema, so the agent can construct valid requests without browsing Twitter's developer documentation.
Time to first call
Direct Twitter API integration: 3-7 days for OAuth 2.0 PKCE setup, rate limit handling, pagination, and stream management. Through Jentic: under 1 hour — search for the operation, load the schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Twitter API v2 API through Jentic.
What authentication does the Twitter API v2 use?
The Twitter API v2 supports three authentication methods: OAuth 2.0 with PKCE for user-context requests (posting tweets, managing DMs), App-only Bearer Token for read-only endpoints (search, user lookup), and OAuth 1.0a User Token for legacy compatibility. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and agents receive scoped tokens without handling raw keys directly.
What are the rate limits for the Twitter API v2 search endpoint?
The /2/tweets/search/recent endpoint allows 450 requests per 15-minute window on Basic access and 300 per 15-minute window on Pro access. Each request returns up to 100 tweets. The /2/tweets/search/all (full-archive) endpoint is available on Academic Research or Pro access at 300 requests per 15-minute window.
Can I stream tweets in real time with the Twitter API v2?
Yes. The /2/tweets/search/stream endpoint provides a persistent HTTP connection delivering tweets matching your filter rules within seconds of posting. You configure rules via POST /2/tweets/search/stream/rules. Basic access supports 25 concurrent rules; Pro access supports up to 1,000 rules.
How do I search tweets and post content through Jentic?
Install the Jentic SDK with pip install jentic, then search for 'search recent tweets' to discover the /2/tweets/search/recent operation. Jentic returns the full input schema so your agent can construct the query parameter. For posting, search 'create a tweet' to load the POST /2/tweets schema. Sign up at https://app.jentic.com/sign-up to get started.
Can I access historical tweets beyond the 7-day window?
Yes. The /2/tweets/search/all endpoint provides full-archive search going back to the first tweet ever posted. This requires Academic Research or Pro access level. The endpoint supports the same query syntax as recent search with additional operators for time-range filtering using start_time and end_time parameters.
Does the Twitter API v2 support sending direct messages?
Yes. Use POST /2/dm_conversations/with/{participant_id}/messages to send a DM to a specific user, or POST /2/dm_conversations to create a new group conversation. Retrieve conversation history with GET /2/dm_conversations/with/{participant_id}/dm_events. DM endpoints require OAuth 2.0 user context with the dm.read and dm.write scopes.
What is the difference between Twitter API v1.1 and v2?
API v2 uses a redesigned data model with expansion fields, supports more granular OAuth 2.0 scopes with PKCE, and adds endpoints for Spaces, Communities, and Bookmarks that do not exist in v1.1. The v2 search endpoint supports a richer query language with conversation_id, context annotations, and entity operators not available in v1.1.
GET STARTED