Solutions · Crypto
Watch crypto accounts on X and get new tweets by webhook
Account monitoring sends new tweets from the accounts you choose to your webhook within 1, 5 or 60 seconds. Search finds everyone else who mentions a cashtag, a ticker or a contract address.
This is a data service. No trading advice, no promise of an edge.
Account monitoring
New tweets from the accounts you watch, pushed to you
You give us a list of X accounts, we read them on a fixed schedule and POST every new tweet to your webhook, signed with HMAC-SHA256. An account many customers watch is read once, which keeps the price per account low.
- The class is the longest gap between two reads; usually we read more often.
- X's own delay and your webhook's response time come on top.
- Every event carries
tweetCreatedAtanddetectedAt, so you can measure the delay yourself.
How fast
Fast monitoring
50 accounts$29per month
- We read at least every
- 5 s
- Typical
- 2–5 s
- About $0.58 per account and month
See all plans
| Accounts | Standard (≤60 s) | Fast (≤5 s) | Real-time (≤1 s) |
|---|---|---|---|
| 10 accounts | $5 | $9 | $19 |
| 50 accounts | $15 | $29 | $59 |
| 250 accounts | $49 | $99 | $199 |
| 1,000 accounts | $149 | $299 | $599 |
| 5,000 accounts | $499 | $999 | $1,999 |
10 accounts
- Standard (≤60 s)
- $5
- Fast (≤5 s)
- $9
- Real-time (≤1 s)
- $19
50 accounts
- Standard (≤60 s)
- $15
- Fast (≤5 s)
- $29
- Real-time (≤1 s)
- $59
250 accounts
- Standard (≤60 s)
- $49
- Fast (≤5 s)
- $99
- Real-time (≤1 s)
- $199
1,000 accounts
- Standard (≤60 s)
- $149
- Fast (≤5 s)
- $299
- Real-time (≤1 s)
- $599
5,000 accounts
- Standard (≤60 s)
- $499
- Fast (≤5 s)
- $999
- Real-time (≤1 s)
- $1,999
Monthly, from your prepaid balance. Monitoring is not billed per request.
- 01
Add the accounts
Up to 100 usernames or IDs per request; each one is confirmed or rejected on its own.
- 02
Set your webhook
A public https address. The answer holds the signing secret you verify every event with.
- 03
Send a test event
A signed test delivery shows that your endpoint answers in time.
Webhook URLs must be public https addresses. Answer with any 2xx within 5 seconds and do the work in a queue; failed deliveries are retried for 24 hours, and GET /monitors/events returns the last 7 days if you would rather pull.
The API calls, signature verification in Node.js, Python and Go, the event format and the retry schedule are in the docs.
Monitoring setup guideMonitoring
Watch tweets arrive the way a monitor sees them
Real tweets from the last 12 hours, mostly by accounts with 20,000+ followers, replayed one by one with a delay. This preview is not live; a monitor watches the accounts you choose, of any size, and POSTs every new tweet to your webhook within 1, 5 or 60 seconds, depending on the class.
Delayed replay of real tweets from the last 12 hours for the selected topic, newest at the top. Each tweet shows when it was posted and how many followers its author has.
Free preview, so tweets arrive with a delay and are not live. Real-time delivery comes with a monitor plan.
Search
Cashtags, tickers and contract addresses
/search is the X search box as an API: anyone mentioning a token, not only accounts you follow. One page of results is one call.
Example search
- Query
- $BTC OR $ETH
- Order
- Latest first
- Engagement
- At least 5 likes
- Leave out
- Replies, and tweets with “giveaway” or “airdrop”
- Format
- Simple: flat tweets with full text, author and counts
- Cashtags are plain text in the query:
$BTC,$SOL OR $JUP. The SDKs encode the$for you. - Contract addresses are matched as text. Quote them:
"0x6982508145454ce325ddbe47a25d4ec3d2311933", and also search the project handle and domain (url:example.xyz). - Only new tweets: add
since_id:with the newest ID you have (orsinceIdinfilters), so a poll returns nothing you already saw. - Less noise:
minimumLikesCount,onlyVerified/onlyBlueVerified,noneOfTheseWords,lang. All keys are in the search reference. - Query plus filters can be up to 512 characters. Square brackets are rejected with 422.
Recipe 1
Poll a cashtag without duplicates
Ask for the newest tweets every 30 seconds and pass the highest ID you have as since_id:. Each tweet arrives once, oldest first, as a flat simple-format object with full text, author and counts.
The SDK retries 429 and 5xx with backoff. Calls that fail with 400, 408, 409 or a 5xx error are refunded.
- 01
Search the newest tweets
One call for the latest page of your cashtag query.
- 02
Print or forward them, oldest first
Skip deleted or protected tweets.
- 03
Remember the highest tweet ID
The next search asks only for tweets after it.
- 04
Wait 30 seconds and repeat
The interval sets the cost; see the costs below.
Recipe 2
Follow a set of accounts with one call
Put the projects, founders and analysts you follow on a public X list. /lists/tweets returns the newest tweets of all members, so one call per poll covers the whole list, however many accounts are on it.
The first run prints the current page; after that only new tweets. Reference: List tweets.
- 01
Make a public X list
Any account can own it; add the accounts you want to follow.
- 02
Read the list's newest tweets
One call returns the latest tweets of all members.
- 03
Pass on only tweets you have not seen
Then wait 15 seconds and read again.
Cost
What a polling interval costs
One query or one list, one page per poll, 30-day month. Every poll is a call whether or not it finds something new, so pick the slowest interval that is fast enough for you.
Poll every
Polling every 30 s
$7.78per month at Standard
- Calls per month
- 86,400
- At Scale ($0.065 / 1k)
- $5.62
At 60 seconds polling yourself is cheaper; at 1 to 5 seconds a monitoring plan is, and you do not run the loop, the deduplication or the retries.
See every interval
| Poll every | Calls per month | Standard | Scale |
|---|---|---|---|
| 1 s | 2,592,000 | $233.28 | $168.48 |
| 5 s | 518,400 | $46.66 | $33.70 |
| 15 s | 172,800 | $15.55 | $11.23 |
| 30 s | 86,400 | $7.78 | $5.62 |
| 1 min | 43,200 | $3.89 | $2.81 |
| 5 min | 8,640 | $0.78 | $0.56 |
1 s
- Calls per month
- 2,592,000
- Standard
- $233.28
- Scale
- $168.48
5 s
- Calls per month
- 518,400
- Standard
- $46.66
- Scale
- $33.70
15 s
- Calls per month
- 172,800
- Standard
- $15.55
- Scale
- $11.23
30 s
- Calls per month
- 86,400
- Standard
- $7.78
- Scale
- $5.62
1 min
- Calls per month
- 43,200
- Standard
- $3.89
- Scale
- $2.81
5 min
- Calls per month
- 8,640
- Standard
- $0.78
- Scale
- $0.56
No code
Alerts in Telegram with n8n
The TwittrAPI community node for n8n ships a keyword monitor that remembers the newest tweet ID, so only new tweets pass. Point it at a cashtag and send the result to Telegram instead of Slack.
- 01
Install the node and add your key
Install the TwittrAPI community node in n8n and add your API key as a credential.
- 02
Import the keyword monitor
Import the ready-made keyword monitor workflow, set the query to your cashtags and the schedule to the interval you priced above.
- 03
Swap Slack for Telegram
Replace the Slack node with Telegram > Send Message, map the tweet text and link, and activate.
The workflow remembers the newest ID only in active (production) runs; manual test runs start fresh. More recipes: No-code workflows.
n8n setup guideFAQ
Crypto tracking questions
Is this financial advice or a trading signal?
No. TwittrAPI delivers public tweets and search results. What they mean, and whether to act on them, is your decision. Nothing on this page promises a trading edge.
How do I search for a contract address?
Put it in double quotes, for example "0x6982508145454ce325ddbe47a25d4ec3d2311933". It is matched as text. New tokens are often mentioned with a shortened address or only a link, so also search the project handle and its domain (url:example.xyz).
How often can I poll?
As often as your rate limit allows: 30 requests per second after your first top-up, 3 on the trial key. Every poll is one call, so the interval sets the cost; the cost section above has the numbers.
Can I follow protected (private) accounts?
No. Only public accounts and what anyone can see on X.
Do I need an X account?
Not for search or for reading a public list. To watch your own selection of accounts with one call, someone has to create a public X list with them; that list can belong to any account.
How fast is real-time monitoring?
We read the lists of Real-time accounts at least once a second, usually every 0.5–1 s. Total delay also depends on X showing the tweet and on your webhook. Each event carries tweetCreatedAt and detectedAt, so you can measure it.
What if my webhook is down?
Deliveries are retried for 24 hours, and the last 7 days of events can be pulled with GET /monitors/events.
Related
Read next
- Search reference →Operators and every filters key/docs/reference/search
- List tweets →Newest tweets of a list's members/docs/reference/lists-tweets
- Simple format →The tweet object your loop receives/docs/simple-format
- Account monitoring →API, events, signatures, retries/docs/monitoring
- Twitter Streaming API alternative →Plans and prices compared/twitter-streaming-api
- Social listening →Mentions, campaigns and trends/use-cases/social-listening
- Rate limits →How many polls per second you can send/docs/helpful-infos/rate-limits
- Pricing →Per-call tiers and rate-limit add-ons/pricing
Watch your first accounts today
$0.10 free credit after sign-up is about 1,100 calls at Standard: enough to tune a query before you poll it.