API reference · v1
Everything an X account does, on one connection
xSignalFeed watches the X (formerly Twitter) accounts you name and sends you what they do as it happens: new posts, replies, reposts, quotes, deletions, profile edits, follows and new verified followers. You can also watch X search for a phrase, and read profiles, posts, followers, lists, communities and trends on demand. One WebSocket carries the events; REST is there for the times you need to ask rather than wait.
Introduction
There are three ways to consume the service. Monitoring: name accounts and keywords, and receive events over a WebSocket or a webhook as things happen. History: read back the events your key received. Reads: ask X for a profile, a post, a search, a list, a community or the trends right now.
Events come in four families. Each has one payload shape, described field by field under Events.
| Category | Types | Meaning |
|---|---|---|
| Posts | tweet.create, tweet.reply, tweet.retweet, tweet.quote, tweet.edit, tweet.delete | What the account publishes: new posts, replies, reposts, quotes, edits, and deletions of any of those |
| Profile | profile.name, profile.screen_name, profile.bio, profile.location, profile.url, profile.avatar, profile.banner, profile.pinned, profile.verified | Any change to what the account shows about itself, with the old and the new value |
| Follow graph | follow.add, follow.remove, followers.verified.add | Who the account starts or stops following, and which verified accounts start following it |
| Account | account.status | Whether the account can be seen at all: protected, suspended, unavailable, or active again |
| Search | search.match | Posts from anyone on X that match a keyword you watch |
Access is by API key. A key carries scopes and caps that come from its plan; GET /v1/account tells you what yours may do. Nothing here is metered by the volume of events: streaming is included, and only on-demand reads consume credits.
xSignalFeed is an independent third-party service. It is not affiliated with, endorsed by, or sponsored by X Corp. We read public data only.
Where next
Quickstart
Check your key, monitor an account and read your first event in four steps.
Core concepts
Targets and keywords, two-frame delivery, at-least-once, replay.
Events
The envelope, every event type, and the five payload shapes field by field.
API reference
One page per endpoint: parameters, response, and a request and response example.