Tracked Account Management
Tracked account management documentation for adding, removing, and operating monitored X/Twitter accounts in TweetStream.
Direct answer
Tracked account management lets teams maintain the selected accounts that power TweetStream alerts through the dashboard or authenticated REST endpoints.
Dashboard workflow
Checkout normally creates the API key automatically. In the dashboard, use the Account Management tab to add the first watchlist, remove old handles, and confirm the account count before connecting a WebSocket client.
- Use handles without
@; input is normalized before syncing - Remove unused handles before adding new ones near your plan limit
- Use
/api/meto verify active handles from your own tools
REST endpoints
API clients use JSON bodies with an accounts field. The value can be one string or an array of strings.
| Endpoint | Method | Body |
|---|---|---|
| /api/add-account | POST | {"accounts":"elonmusk"} or {"accounts":["elonmusk","naval"]} |
| /api/remove-account | DELETE | {"accounts":"elonmusk"} or {"accounts":["elonmusk","naval"]} |
| /api/me | GET | No body; returns current account, plan, and usage snapshot |
Propagation behavior
Account changes can take a short propagation window while tracking state syncs. Treat retries as idempotent: retry the same desired add or remove, then use /api/me or the dashboard count as the source of truth.
Dashboard vs REST
Dashboard management is best for onboarding and trial setup. REST management is best when your own system controls watchlists programmatically.
- Use dashboard setup for first watchlists
- Use REST for automated account rotation
- Use plan limits to avoid exceeding account capacity
Questions
Start real-time Twitter WebSocket alerts today
WebSocket delivery, OCR, and token detection - no infrastructure to build.
From $199/mo · Minimum/Pro 3-day trial · OCR + token detection included
Related Pages
