Product · Twitter account monitor
Monitor Twitter accounts without running your own poller.
Watch public X/Twitter accounts and receive new posts in Discord or a generic signed webhook. xfetch handles dashboard setup, delivery dedupe, and bounded retries so your team can react to the post, not the polling infrastructure.
content-type: application/json x-xfetch-event-id: evt_... x-xfetch-delivery-id: dlv_... x-xfetch-timestamp: 2026-06-29T12:34:56Z x-xfetch-signature: v1=<hmac-sha256>
{
"type": "tweet.created",
"event_id": "evt_...",
"delivery_id": "dlv_...",
"monitor": { "account": { "username": "acme" } },
"tweet": { "id", "text", "created_at" }
}How it works
Choose public accounts
Create one monitor slot per account from dashboard suggestions or by resolving an exact public @handle.
Attach delivery
Send posts to one Discord incoming webhook and one generic signed webhook per monitor slot.
React to new posts
xfetch dedupes deliveries and retries failed sends with bounded backoff, so your system reacts without running a poller.
Use it when new posts are the trigger
Account monitoring is the reactive side of xfetch. Use the monitor as the wake-up signal, then call the read API for deeper context when your workflow needs it.
Free and PAYG include 1 10-day trial slot. Monthly plans include Starter 2, Growth 5, Pro 10, and Scale 25 monitor slots.
See all plans →Founder and competitor alerts
Push new posts from high-signal accounts into Discord channels your team already watches.
Trading and research desks
Trigger internal workflows when selected public accounts publish, then fetch deeper context through /v1 reads.
AI and agent workflows
Use account monitors as the wake-up signal, then let your agent call /v1 for profile, tweet, or conversation context.
Customer or community updates
Watch public accounts that matter to your product and route new posts into your own webhook pipeline.
Clear boundaries
- Dashboard-configured only: there is no public monitor configuration API.
- Account-only today: no keyword monitor, saved search monitor, or broad account-search workflow.
- No replay endpoint or guaranteed redelivery promise; use normal /v1 reads to recover context if needed.
- Generic webhooks are signed with x-xfetch-signature; Discord incoming webhook messages are not signed.
Account monitor FAQ
- What is a Twitter account monitor?
- A Twitter account monitor watches selected public X/Twitter accounts and sends a delivery when a watched account posts. In xfetch, setup happens in the dashboard, and deliveries can go to Discord incoming webhooks or generic signed webhooks.
- Can I monitor any Twitter account?
- You can start from suggested accounts or resolve an exact public @handle in the dashboard add flow when you have available monitor slots. Each monitor slot watches one account.
- Do account monitors cost API credits?
- No. Monitor deliveries are not credit-metered. Free and PAYG accounts get one 10-day trial slot, monthly plans include monitor slots, and additional accounts are $3 per account per month.
- Can xfetch monitor Twitter keywords?
- Not today. xfetch account monitors watch accounts, not keywords or saved searches. For keyword and topic workflows, use the /v1 search endpoints and normal pagination.
- Are webhook deliveries guaranteed?
- No. xfetch retries failed deliveries with bounded backoff, but it does not promise guaranteed redelivery or expose a replay endpoint. Generic webhook deliveries are signed so your receiver can verify they came from xfetch.