Twitter APIs for AI Agents
Social MediaSocial PublishingSource ControlOfficial Vendor DocumentsBearer tokenOAuth 2.0No authAgent Ready
For Agents
APIs2 in catalogue
Endpoints192 indexed
AuthBearer token / OAuth 2.0 / No auth
ProvenanceOfficial OpenAPI documents
An agent can post and thread tweets, run keyword and full-archive searches, open real-time filter streams, send direct messages, and read users, lists, communities, and Spaces through the v2 API, while using the v1.1 API to update account settings, profiles, delivery devices, and blocks and to check rate-limit status.
Twitter exposes two API generations side by side: the v2 API with the modern search, stream, DM, and community endpoints, and the v1.1 API that still carries account and profile administration operations. An agent can pick the generation that has the operation it needs rather than being forced onto a single surface.
Use for: Posting and searching tweets, real-time streaming, direct messaging, and account and profile administration on Twitter
Not supported: ad campaign management, analytics dashboards, audience insights, payments
Credentials: Authentication is per generation: the v2 API uses App-only Bearer Token or OAuth 2.0 with PKCE, while the v1.1 API surface as specified carries no declared authentication, so a single credential does not cover both.
All 2 Twitter OpenAPI documents are vendor-official and indexed by Jentic, kept validated and agent-ready.
Twitter offers two API generations for programmatic access to the platform. The Twitter API v2 covers 109 endpoints for posting tweets, searching recent and full-archive conversations, streaming filtered content in real time, sending direct messages, and reading users, lists, communities, and Spaces. The legacy Twitter API v1.1 covers 83 endpoints focused on account settings, profile updates, delivery devices, blocks, and application rate-limit status. Together they let an agent read, publish, monitor, and administer content and accounts on Twitter.
Twitter API Catalog
2 APIs across 2 product groups.
Which Twitter API should I use?
| I want to... | Use |
|---|---|
| Post, search, or stream tweets and send direct messages | Twitter API v2 |
| Update account settings, profile, or delivery device | Twitter API |
| Check application rate-limit status | Twitter API |
| Read users, lists, communities, and Spaces | Twitter API v2 |
Install Jentic One Beta
Connect the Twitter APIs to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Twitter APIs, 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftwitter.com" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftwitter.com" | 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.
Once connected, ask your agent something like: “post, search, and monitor tweets on Twitter”.
What AI Agents Can Do with Twitter
Each workflow spans multiple Twitter APIs. Jentic routes each operation to the right API automatically.
Publish content and administer the account
An agent updates the account profile and settings through the v1.1 API, then publishes tweets and threads through the v2 API. This keeps profile administration and content publishing in one workflow across both generations.
Example prompt:
Call POST /account/update_profile.json on the v1.1 API to set the bio, then post an announcement tweet via POST /2/tweets on the v2 API
APIs used
Twitter API v2 + Twitter API
Monitor mentions while respecting rate limits
An agent searches recent tweets through the v2 API and checks the current rate-limit window through the v1.1 application status endpoint before scaling up polling. This pairs live monitoring with a rate-limit safeguard.
Example prompt:
Call GET /application/rate_limit_status.json on the v1.1 API, then run GET /2/tweets/search/recent on the v2 API for '@acme' if the search window has capacity
APIs used
Twitter API v2 + Twitter API
Manage blocks and moderate conversations
An agent reads a user and their conversation through the v2 API, then applies account-level block operations through the v1.1 API to moderate unwanted interactions. This links conversation lookup with account moderation controls.
Example prompt:
Look up the user with GET /2/users/{id} on the v2 API, then apply the block via the v1.1 blocks operation
APIs used
Twitter API v2 + Twitter API
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring both Twitter generations by hand means pointing at two hosts, choosing Bearer or OAuth 2.0 for the v2 API, and matching each v1.1 operation to its form-encoded fields. Through Jentic you install once, add the Twitter APIs you need from the Jentic directory, store each credential once, and your agent calls them.
Permission scoping
Tweets, direct messages, and profile changes carry their targets in the request body, so you scope your agent to the operations it needs, such as searching recent tweets or reading account settings. A write like posting a tweet or updating a profile is not included unless you add it.
Credential isolation
Your Twitter Bearer token and OAuth 2.0 credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search the Jentic directory by intent such as 'search recent tweets about a brand' or 'update the account profile', and Jentic returns the matching Twitter operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
FAQs
Specific to using Twitter APIs through Jentic.
What can an agent do across Twitter's two APIs?
Across the v2 and v1.1 APIs an agent can post and thread tweets, search recent and full-archive conversations, open real-time filter streams, send direct messages, read users, lists, communities, and Spaces, and update account settings, profiles, delivery devices, and blocks.
What is the difference between the Twitter API v2 and the v1.1 API?
The v2 API uses a redesigned data model with expansion fields, OAuth 2.0 scopes with PKCE, and endpoints for search, streams, DMs, Spaces, and Communities. The v1.1 API is the older generation and covers account and profile administration operations such as settings, profile updates, and delivery devices.
Which API should an agent choose for a given task?
Use the v2 API for tweet publishing, search, real-time streaming, direct messaging, and reading users, lists, communities, and Spaces. Use the v1.1 API for account settings, profile and delivery-device updates, blocks, and reading application rate-limit status.
Do both Twitter APIs share one credential?
No. The v2 API uses App-only Bearer Token or OAuth 2.0 with PKCE, while the v1.1 API surface as specified declares no authentication. Each generation is configured separately in your Jentic One instance.
Can an agent monitor tweets in real time?
Yes. The v2 API provides a persistent filtered stream through /2/tweets/search/stream, with rules configured through /2/tweets/search/stream/rules. Basic access supports 25 concurrent rules and Pro access supports up to 1,000.
Can an agent access historical tweets beyond seven days?
Yes. The v2 API full-archive search endpoint /2/tweets/search/all returns tweets going back to the earliest posts and supports start_time and end_time filtering. It requires Academic Research or Pro access level.
What is out of scope for these APIs?
These APIs do not cover ad campaign management, analytics dashboards, audience insights, or payments. They focus on tweet content, search and streaming, messaging, and account and profile administration.
If you need a different Social Media vendor
All 3 are in the Jentic catalogue with the same one-credential, intent-search pattern.
BOOK A DEMO
Start Connecting APIs to Your AI Agents
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.