Twitter API v2

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. Run it through Jentic One, the self-hosted execution layer.

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.

Can I limit what my agent is allowed to do with the Twitter API v2?

Yes. Jentic One is self-hosted, so your own rules decide which Twitter API v2 operations and credentials the agent may use. You can scope it to read-only work like searching recent tweets or looking up a user, and a write such as posting a tweet or sending a direct message is not included unless you explicitly add it. Because your Twitter token and OAuth 2.0 credentials are injected at execution time rather than handed to the agent, the agent can only call the operations you have granted.