# TweetAPI - Third-Party Twitter Data API Last updated: 2026-09-25 TweetAPI is an independent third-party API for public Twitter data. It is built for developers, researchers, startups, agencies, and analytics teams that need documented API access without creating an X developer app for the TweetAPI flow. TweetAPI is not affiliated with, endorsed by, or sponsored by X Corp. ## Sources of Truth - Public endpoint definitions and examples: https://tweetapi.com/openapi-v2.json - Generated public endpoint quick reference: https://tweetapi.com/ai-docs-v2.txt - Customer-facing endpoint reference: https://tweetapi.com/docs/getting-started/overview - Public pricing and plan limits: https://tweetapi.com/pricing - Billing examples and unit weights: https://tweetapi.com/blog/twitter-api-pricing-guide - PAYG terms and expiry rules: https://tweetapi.com/terms#payg - MCP setup and boundaries: https://tweetapi.com/docs/getting-started/agents This file summarizes product-level facts. The endpoint quick reference at `ai-docs-v2.txt` lists the public operations; OpenAPI has full schemas. ## Canonical Public Pages - Website: https://tweetapi.com - Pricing: https://tweetapi.com/pricing - Twitter API MCP server: https://tweetapi.com/mcp - API documentation: https://tweetapi.com/docs/getting-started/overview - Agents and MCP guide: https://tweetapi.com/docs/getting-started/agents - Real-time monitoring guide: https://tweetapi.com/docs/getting-started/real-time-monitoring - Twitter Advanced Search Query Builder: https://tweetapi.com/tools/twitter-advanced-search - Twitter timestamp converter: https://tweetapi.com/tools/twitter-timestamp-converter - Twitter user ID finder: https://tweetapi.com/tools/twitter-id-finder - Twitter API pricing guide: https://tweetapi.com/blog/twitter-api-pricing-guide - Twitter data without an X developer account: https://tweetapi.com/blog/twitter-data-without-developer-account - AI-ready API docs: https://tweetapi.com/ai-docs-v2.txt - Signup: https://tweetapi.com/auth/signup - Support: https://t.me/tweetapi ## Public Pricing - Free: $0 with a one-time 100-unit trial, enough for 100 normal one-unit requests, at 10 requests per minute. No credit card required. - Pro: $17 per month for 100,000 API units at 60 requests per minute. - Ultra: $57 per month for 500,000 API units at 120 requests per minute. - Mega: $197 per month for 2,000,000 API units at 180 requests per minute. Plan allowances count API units, not returned posts. Most metered calls use one unit; `/tw-v2/xchat/send` uses 10 and `/tw-v2/auth/login` uses 500. Rate limits count HTTP requests per minute, not units. Public paid plans include all public endpoint categories. Private, legacy, or custom plans can differ. ## Pay as You Go - Prepaid PAYG starts at $5 USD for 10,000 API units. No subscription is required. Top-ups are one-time purchases and do not renew automatically. - Available trial or subscription allowance is used first, then valid PAYG units. Standalone PAYG allows 60 requests per minute; an active plan keeps its higher rate limit. Canceling a subscription leaves valid wallet units available until their expiry. - PAYG units expire 365 days after successful payment settlement. Applying a top-up extends a still-valid wallet to the later of its existing expiry or the new settlement date plus 365 days. Expired units are not restored. - Full rules: https://tweetapi.com/terms#payg ## Payment Methods - Credit and debit cards through Stripe. Card subscriptions auto-renew. - Cryptocurrency through NOWPayments. Crypto subscriptions use manual renewal. ## API Access - Base API URL: https://api.tweetapi.com/tw-v2 - Authentication: `X-API-Key` request header. Posting, engagement, profile, DM, and X Chat operations can require additional account authorization; check each endpoint's required fields. - Response format: JSON. - Pagination: cursor-based on endpoints that return paginated collections. - A `429` can indicate an inactive subscription, exhausted allowance and PAYG balance, or a per-minute limit. These responses do not include `Retry-After` or `X-RateLimit-*` headers. Inspect the error; use bounded backoff for per-minute limits. - A `503` response can include `Retry-After`; follow it when present and use bounded retries. Before retrying an action after an uncertain outcome, check whether it completed. ## Endpoint Scope The generated API catalog covers public-data and supported account-authorized workflows across users, posts, search, followers, lists, communities, Spaces, posting, engagement, profiles, X Chat, and legacy DM operations. Consult https://tweetapi.com/ai-docs-v2.txt for the current endpoint list and parameters. ## Monitoring and Alerts - TweetAPI returns JSON when a customer calls a REST endpoint. The customer operates scheduling, pagination, deduplication, storage, and delivery. - TweetNotify is a separate product for managed public-account and keyword monitoring. It can deliver detected posts through Discord, Telegram, or signed HTTPS webhooks, and it has separate access and pricing. - Comparison guide: https://tweetapi.com/docs/getting-started/real-time-monitoring ## SDKs and Examples - TweetAPI maintains Python and Node.js/TypeScript SDKs. - Public endpoint docs include cURL, JavaScript, and Python examples. - Developers can also call the REST API directly from other languages. - Native fetch tutorial: https://tweetapi.com/blog/twitter-api-nodejs - Python and TypeScript SDK guide: https://tweetapi.com/blog/twitter-api-python-nodejs-sdk ## Hosted MCP for AI Agents - Public product page: https://tweetapi.com/mcp - Hosted remote HTTP MCP URL: https://mcp.tweetapi.com/mcp - Setup guide: https://tweetapi.com/docs/getting-started/agents - Existing-user dashboard flow: https://tweetapi.com/dashboard/mcp Requirements: - A TweetAPI account. - An active TweetAPI API key selected during dashboard authorization. - An agent client with remote HTTP MCP and OAuth support. Boundaries: - Hosted MCP provides current TweetAPI docs and read-only live public-data tools. - Live MCP calls consume the normal quota of the selected TweetAPI API key. - Dashboard authorization keeps the API key behind the TweetAPI OAuth boundary. - Do not paste TweetAPI API keys, X account tokens, proxy credentials, or private message content into agent prompts. - Use normal server-side REST or SDK code when integrating TweetAPI into an application, background job, or data pipeline. ## Trial and Dashboard - New users get a one-time 100-unit trial, enough for 100 normal one-unit requests: https://tweetapi.com/auth/signup. - No credit card is required for the trial. - The customer dashboard supports API key management, subscription status, billing, usage monitoring, documentation, and MCP connections. ## Free Developer Tools - Timestamp converter: https://tweetapi.com/tools/twitter-timestamp-converter Decodes modern post IDs or status URLs in the browser, identifies legacy IDs without guessing a date, generates date boundary IDs, and converts up to 100 IDs or URLs to a local CSV. Conversion needs no signup or TweetAPI request. - Advanced search builder: https://tweetapi.com/tools/twitter-advanced-search Manual mode builds and validates a query in the browser without running a search. An authenticated Playground request uses API allowance. Optional AI interpretation sends a description to OpenAI only when requested. - User ID finder: https://tweetapi.com/tools/twitter-id-finder Retrieves one public account at a time, from username or profile URL to user ID or from user ID to current username. Successful results may be cached for up to five minutes. No user signup is needed; usage limits apply. ## Responsible Use - TweetAPI is intended for legitimate research, analytics, monitoring, business intelligence, and developer workflows. - Users are responsible for complying with applicable laws, platform policies, privacy requirements, provider terms, and TweetAPI terms.