# TwitterAPI.io

> Real-time X (Twitter) API for developers. Three pillars: a comprehensive REST API for tweets, profiles, and search; a Stream service that pushes second-level real-time tweets from specific X accounts; and a Custom Rules engine that watches X and forwards any tweets matching your keyword or search conditions. All delivered through Webhook or WebSocket. Pay per call, no minimums, no rate-limit ceilings.

## Three core capabilities

### 1. API — comprehensive Twitter data access

The core capability: REST endpoints for everything you can read or write on X (Twitter). Tweet search, advanced search with date and keyword filters, tweet detail and replies, user profiles, follower / following lists, communities, direct messages, lists, spaces, and write actions (post, like, follow, retweet, bookmark). Battle-tested at over 1B production API calls. Reference documentation:

- [API introduction and overview](https://docs.twitterapi.io/introduction)
- [Authentication](https://docs.twitterapi.io/authentication)
- [Tweet endpoints](https://docs.twitterapi.io/) — search, get by id, replies, quote, retweeters, advanced search
- [User endpoints](https://docs.twitterapi.io/) — profile, followers, following, mentions, last tweets, verified followers
- [Write actions](https://docs.twitterapi.io/) — create / delete tweet, like, retweet, follow, bookmark, send DM
- [Communities](https://docs.twitterapi.io/) — create, join, leave, fetch members and moderators

### 2. Stream — real-time monitoring of specific X accounts

Subscribe to a list of X accounts and receive every new tweet, reply, or mention from those accounts within seconds. Delivery via your own Webhook endpoint or a managed WebSocket. No polling, no missed tweets, no rate-limit headaches.

- [Stream product page](https://twitterapi.io/twitter-stream)
- Endpoints: `add_user_to_monitor_tweet`, `get_user_to_monitor_tweet`, `remove_user_to_monitor_tweet`

### 3. Custom Rules push — keyword / condition-based delivery

Define rules with keywords, advanced search syntax, or scheduled conditions. The system watches X (Twitter) continuously and pushes any matching tweets to your Webhook endpoint as they appear.

- [Custom Rules product page](https://twitterapi.io/tweet-filter-rules)
- Endpoints: `add_webhook_rule`, `get_webhook_rules`, `update_webhook_rule`, `delete_webhook_rule`

## Pricing & operations

- [Pricing](https://twitterapi.io/pricing): pay-per-use. Tweets $0.15 per 1K, profiles $0.18 per 1K, followers / following from $0.01 per 1K (tiered by page size), bulk follower IDs from $0.0045 per 1K. No minimums, no contracts.
- [QPS limits](https://twitterapi.io/qps-limits): per-plan rate and burst behavior, up to 200 QPS per client.
- [Status](https://twitterapi.io/status): live system health.
- [Changelog](https://twitterapi.io/changelog): recent platform changes.

## Comparison

- [TwitterAPI.io vs Apify](https://twitterapi.io/compare/vs-apify): cost, latency, and rate-limit comparison versus Apify scrapers.

## Policies

- [Terms of Service](https://twitterapi.io/terms)
- [Privacy Policy](https://twitterapi.io/privacy)
- [Acceptable Use Policy](https://twitterapi.io/acceptable-use)
- [Refund Policy](https://twitterapi.io/refund-policy)

## Other

- [Blog](https://twitterapi.io/blog) — tutorials, integration guides, and platform writeups.
- [Affiliate program](https://twitterapi.io/affiliate-program) — refer developers and earn revenue share.
- [Contact](https://twitterapi.io/contact) — support, partnership, or press.