Skip to main content
GET
Twitter Keyword Monitor List & Tracked Searches

Reconcile the Entire Keyword Monitor Portfolio

Use this endpoint when the exact monitor ID is unknown. It returns up to 200 stored searches plus total. It does not paginate the inventory. Use the detail endpoint only after choosing one monitor ID from this inventory.
Free - does not consume credits
The cURL, Node.js, Python, and Go examples convert each keyword monitor into one inventory row. Store keyword_monitor_id, query, event_types, is_active, next_billing_at, events_endpoint, event_detail_endpoint_pattern, verify_endpoint, update_endpoint, delete_endpoint, webhooks_endpoint, and deliveries_endpoint_pattern before reconciling events, webhooks, or paused queries.

Inventory handoff

Use GET /monitors/keywords after create, update, pause, or delete operations to rebuild your keyword monitor inventory. The response returns up to 200 keyword monitors ordered by creation time and a total count for the returned set.

Active Burn

Filter monitors where isActive is true. Each active keyword monitor bills 21 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 keywordMonitorId with List Events to audit stored monitor events. Use Get Event for one event’s full payload.

Delivery Audit

Use List Deliveries when webhook delivery evidence must be retained. Join delivery streamEventId to event IDs. Do not use x_event_id as the delivery join key.

Detail Check

Use Get Keyword Monitor before changing a row. Store the returned query, eventTypes, isActive, and nextBillingAt.

State Repair

Use Update Keyword Monitor to replace eventTypes or toggle isActive. Use Delete Keyword Monitor only when the query should stop permanently.

Review a Portfolio of Tracked Search Rules

Use the returned list to inspect every stored Twitter keyword query. Start with total, then count the emitted monitors rows. Store the snapshot time beside both values. A later comparison needs a complete inventory. Classify each query by its actual search intent. Separate brand handles, product names, campaign hashtags, support phrases, and competitor terms. Keep the original query text. Do not replace it with a dashboard label. Group identical normalized queries before changing anything. Two active rows can watch the same phrase with different event types. Compare eventTypes before calling them duplicates. Preserve intentional routing differences. Next, separate active and paused rows. Active rows can create new matching events. Paused rows remain useful for history and later reactivation. Never infer activity from an empty event window alone. Compare every active row with webhook subscriptions. Flag missing event types, unused webhook event types, and absent receiver ownership. Use the monitor ID to inspect stored events. Use event IDs to inspect delivery attempts. Finish with one inventory record per keyword monitor. Keep the monitor ID, query, event types, active state, creation time, and billing checkpoint. Add the responsible team and review date outside the API response.

Prepare a Keyword Monitor Budget Report

Count only active keyword monitors when estimating hourly monitor use. Each active monitor bills 21 credits per active monitor-hour. Listing the inventory remains free. Sort active rows by nextBillingAt. This reveals the next billing checkpoints without changing monitor state. Join each row with its owner and campaign end date. Pause expired campaigns through the update route. Keep paused monitors outside the active-burn total. Keep deleted monitors outside the current inventory. Preserve separate history when compliance or support needs older event evidence. Rebuild the report after every create, update, pause, resume, or delete. Compare complete snapshots by monitor ID. Report new, reactivated, paused, and removed queries separately. This prevents one aggregate count from hiding state changes.

Headers

string
required
Your API key. Session cookie authentication is also supported. Generate a key from the dashboard.

Response

200 OK

object[]
Array of keyword monitor objects.
string
Unique keyword monitor ID.
string
Normalized X search query.
string[]
Subscribed event types.
boolean
Whether the monitor is currently active.
string
ISO 8601 creation timestamp.
string
Next hourly credit charge time for active monitor billing.
number
Total number of keyword monitors.

401 Unauthenticated

Missing or invalid API key.

429 Rate Limited

Too many requests. Wait for the Retry-After header before retrying.
Returns up to 200 keyword monitors. There is no pagination. Contact support if you need more.
Related: Create Keyword Monitor to add a query, Get Keyword Monitor to fetch one monitor, Update Keyword Monitor to pause or edit it, Delete Keyword Monitor to remove it, List Events and Get Event to audit events, or List Webhooks and List Deliveries to audit delivery evidence.