GET https://xquik.com/api/v1/monitors
Inventory every Twitter account monitor
UseGET /monitors when you monitor multiple Twitter accounts.
It returns up to 10,000 account monitors in one response.
The route lists only monitors that belong to the signed-in user. Each
row identifies one tracked X profile. It also shows enabled event types and
the active state. The row includes its creation time. Check
nextBillingAt for the next active-monitor charge. Use the single-monitor
route for one known ID.
Group rows by username or stable xUserId. Keep eventTypes with every row
because two monitors can track different changes. Separate inactive monitors
before calculating which profiles still produce events.
Store monitorId before handing a row to event or webhook processing. Event
queries use that ID to isolate the monitor’s events. Webhook deliveries
remain separate from monitor inventory.
Review nextBillingAt before enabling more monitors. Listing is free, but
active monitors consume credits each hour. Delete unused monitors. Do not call
a monitor idle after one empty event window.Free. This endpoint does not consume credits.
How do you monitor multiple Twitter accounts?
Create one account monitor for each X (Twitter) username. Select only the required tweet and profile event types. Then call this route to rebuild the complete list. Store each returnedid as the stable monitor key. Keep xUserId beside the
username because an account can change its username.
Use isActive to filter rows before estimating costs.
Group active rows by owner, workflow, or webhook receiver. Keep paused rows in
the same inventory because their configuration still exists.
Use List Events to retrieve stored events for one
monitor. Pass the returned monitor ID as monitorId. Use
List Webhooks to inspect receivers. Use
List Deliveries to audit each delivery.
This route lists monitor settings, not stored events.What does the monitor inventory include?
Each row shows the monitor ID, username, and stable X (Twitter) user ID. Use that user ID for account joins. TheeventTypes array lists the changes the monitor tracks.
The isActive field separates running monitors from paused ones.
The timestamps show when Xquik created the monitor and its next billing point.
Tweet filters cover new posts, replies, quotes, reposts, media, and links. They
also cover polls, mentions, hashtags, and long-form posts. Profile filters
include the avatar, banner, name, username, biography, and location. They also
cover URL, verification, protection, pinned tweets, and account availability.
Activity filters cover deleted posts, live videos, and Spaces. Follow filters
cover follows, new and lost followers, and follower and following counts.
Read eventTypes from every row. Do not assume every monitor uses identical
filters.
The response also includes total. Compare it with the emitted monitor count.
A mismatch usually means the client dropped rows during local processing. The
route returns up to 10,000 monitors per page. When hasMore is true, pass
nextCursor as cursor to read the next page.Does this route return tweets or analytics?
No.GET /monitors returns account-monitor configurations. It does not return
tweet timelines, engagement totals, audience reports, or sentiment scores.
Use List Events for stored monitor events. Use Get Event to inspect one stored event.
The route also does not publish or schedule posts. Use the
X Write API for publishing workflows.
Do not use the monitor list as an event feed or a publishing queue.How do you set alerts for several X accounts?
First, create one monitor per username. Give each monitor only the event types its receiver understands. Then create a webhook for the matching event types. Store the monitor ID with every workflow rule. You can then tell the source when several profiles send similar events. Re-list monitors after every create, update, pause, or delete operation. Check that the intended row exists and has the expectedeventTypes. Confirm
isActive before waiting for a new alert. Paused monitors retain their
settings. They stop polling until reactivated.
Audit webhook deliveries separately. Join a delivery to its stored event with
the documented event ID. Do not infer success from the monitor’s active state.
Polling state and webhook delivery status are separate.How should teams manage many tracked profiles?
Assign one owner when managing multiple Twitter accounts. Store that owner outside the API response. Save the monitor ID, X (Twitter) user ID, selected event types, and active state. Add the owner and review date. Assign ownership by workflow. Support teams can process replies and mentions. Research teams can own new posts, quotes, or media events. Account teams can own profile-name, biography, verification, or availability changes. Match each assignment to the exacteventTypes returned for that monitor.
Agencies should separate client profiles before reporting active-monitor
costs. Review paused and active rows together, but count their costs
separately. Record every approved state change. With that history, a cleanup for one
client cannot change another client’s monitor.Is listing Twitter account monitors free?
Yes. ThisGET request consumes no credits. Active monitors cost 30 credits
per monitor-hour. Paused monitors stay listed and stop active-monitor billing.
Review isActive and nextBillingAt before enabling more profiles.
A quiet event window is no reason to cut cost. A valid monitor may receive
no matching event during that period. Confirm its owner and selected filters
before pausing it. Delete a monitor only when its configuration is no longer
required.Inventory handoff
UseGET /monitors after create, update, pause, or delete operations. That
rebuilds your account monitor inventory. The response returns up to 10,000 monitors
ordered by creation time. It also returns a total count for the returned set.Tracked accounts
Store each monitor’s
id, username, and xUserId with your CRM,
warehouse, or queue records.Detail handoff
Get Monitor
returns one account monitor’s latest event filter, active state, and billing
checkpoint. Use it with each
id when a support workflow needs any of them.Active billing
Filter monitors where
isActive is true. Each active account monitor
bills 30 credits per active monitor-hour. Use nextBillingAt to schedule
credit checks or pause stale alerts.Webhook alignment
Compare each monitor’s
eventTypes with List Webhooks
before relying on signed alerts.Event backfill
Use
id as monitorId with List Events to
audit stored account monitor events. Open one returned ID with
Get Event to inspect the complete stored event.Delivery audit
Use List Deliveries for each webhook
and join delivery
streamEventId to event IDs. Do not use x_event_id as
the delivery join key.State repair
Use Update Monitor to replace
eventTypes
or toggle isActive. Use Delete Monitor
only when the tracked account should stop permanently.Reconcile an account monitor inventory
Store one row per monitor ID. Include its username, X (Twitter) user ID, and event types. Add the active state and billing date. Join monitors to webhooks by configured ownership. Flag missing webhooks, extra webhooks, and mismatched event types. Compare completed snapshots to identify new, paused, resumed, or removed monitors. Do not compare incomplete snapshots. Use the single-monitor route for an incident review. Update only the monitors approved for change.Assign account monitor ownership
Use the complete list to assign every tracked X profile. Start with monitor ID,username, and stable xUserId. Keep the stable ID when a username changes.
Group rows by the team consuming their events. Support teams may own reply and
mention events. Research teams may own new posts. Account operations may own
profile changes. Store ownership outside returned API fields.
Compare eventTypes with the events each receiver handles. A webhook receiving only
tweet events cannot process a profile biography change. Flag missing
subscriptions before calling the monitor healthy.
Then inspect active state. Active monitors can produce new account events.
Paused monitors keep their configuration and do not poll. Keep both groups in
the inventory. Never treat a paused row as deleted.
Use nextBillingAt for active-budget reviews. Listing remains free. Count
active account monitors separately from keyword monitors. They track different targets and
event types.
Publish one ownership row per monitor ID. Include username, X (Twitter) user ID, event
types, active state, and billing checkpoint. Add its owner and review date.
Later monitor changes then show up as changed rows.Prepare a bulk account monitor cleanup
Begin from one complete list response. Do not combine partial snapshots. Mark rows lacking an owner, current workflow, or required webhook subscription. Inspect recent stored events before proposing a pause. An empty window does not prove the profile is irrelevant. Confirm the account, event types, and review window with the owner. Pause monitors through the update route first. Keep their IDs and previous event types in the change record. Watch receiver queues before you delete. Delete only approved rows. Re-list monitors after every batch. Confirm removed IDs are absent and paused IDs remain present. Record billing checkpoints for the remaining active rows. Handle uncertain changes individually. Use the single-monitor status route for each affected ID. Never replay a bulk delete because the client lost its local response.Headers
Query parameters
Response
200 OK
400 Invalid cursor
{ "error": "invalid_input", "message": "Cursor invalid. Use nextCursor from the previous page, or omit it to start over." }
The cursor is not one this list returned. Send the nextCursor of the previous page, or omit it.401 Missing API key
Missing or invalid API key.429 Rate limited
{ "error": "rate_limit_exceeded", "message": "Too many requests. Try again later.", "retryAfter": 1 }
Too many requests. Wait for the Retry-After header before retrying.Returns up to 10,000 monitors per page. Pass
nextCursor as cursor for the next page.Related.
- Create Monitor to add a new monitor.
- Get Monitor to fetch one monitor.
- List Events to audit stored events.
- Get Event to inspect one event.
- List Webhooks to compare subscriptions.
- List Deliveries to audit webhook delivery status.
Response examples
- 400
{ "error": "invalid_input", "message": "Invalid input. Check the request body." } - 401
{ "error": "unauthenticated", "message": "Authentication required. Provide a valid API key or bearer token." } - 403
{ "error": "api_key_paused", "message": "This API key is paused. Resume it at dashboard.xquik.com/api-keys to use it again." } - 429
{ "error": "rate_limit_exceeded", "message": "Too many requests. Try again later.", "retryAfter": 60 }