API reference

Base URL https://api.xsignalfeed.com. All responses are JSON in the envelope described under Errors when they fail, and carry the headers listed under Rate limits when they succeed. Fields marked * are required.

Monitoring

Choose which accounts this key follows. For each of them you get every event type your key allows, or only the types you pick.

Keywords

Watch X search for phrases. The query accepts X's own syntax: exact phrases in quotes, OR, -exclusions, #hashtags, $cashtags, from:, to:, lang:, filter:media, -filter:replies, -filter:retweets. We watch the "Latest" tab, so results are chronological, and any language or script works.

EndpointNameScopeCredits
GET /v1/keywordsList keywordskeywords:read0
POST /v1/keywordsWatch a keywordkeywords:write0
DELETE /v1/keywords/{keyword_id}Remove a keywordkeywords:write0

Stream & history

The WebSocket is described under Streaming; this is its REST companion for catching up.

EndpointNameScopeCredits
GET /v1/eventsEvent historyreplay0

Users

Profiles, follow lists, media, mentions, subscriptions and user search, read from X now. Each call costs the credits shown.

Tweets

Posts by id, with their replies, quotes, reposters, thread and article. Each call costs the credits shown.

X search in its own syntax, latest or top results, paged.

EndpointNameScopeCredits
GET /v1/searchSearch postsreads2
GET /v1/search/trendsSearch a trendreads2

Lists

Timeline and membership of any public list.

Communities

Info, members, moderators and posts of an X community.

What is trending on X right now, by category.

EndpointNameScopeCredits
GET /v1/trendsGet trendsreads2

Account

What this key may do, how much it has used, where webhooks go.

Meta & status

Public, cached for five minutes, no key needed. Build your validation and your UI from these instead of copying this page.

A machine-readable description of all of the above is at /v1/openapi.json; /v1/docs redirects here.