Monitors
Twitter keyword monitor updates & alert controls
Update a keyword monitor’s tweet event types or pause and resume it. The X search query stays fixed, so the monitor ID and stored events remain usable.
- 200
- 400
- 401
- 403
- 404
- 429
PATCH
Twitter keyword monitor updates & alert controls
When to update a keyword monitor
Use this route to change one keyword monitor’s event types or active state. Use get to read one monitor. Use list to see every keyword monitor on the account.Free. This endpoint does not consume credits.
keyword_monitor_id, query, event_types,
is_active, next_billing_at, verify_endpoint, delete_endpoint,
events_endpoint, event_detail_endpoint_pattern, webhooks_endpoint, and
deliveries_endpoint_pattern. Do this before resuming alerts or webhook checks.
Path parameters
string
required
The unique keyword monitor ID.
Headers
string
required
Your API key. Session cookie authentication is also supported. Generate a key from the dashboard.
string
required
Must be
application/json.Body
At least 1 field is required.string[]
Updated array of event types. Must contain at least 1 valid keyword monitor
type. Valid types are
tweet.new, tweet.quote, tweet.reply, tweet.retweet,
tweet.media, tweet.link, tweet.poll, tweet.mention,
tweet.hashtag, tweet.longform.string | null
New label for the monitor, 1 to 80 characters. Send
null to remove the label. The next event carries the new monitorName.boolean
Set to
false to pause monitoring, or true to resume. Paused keyword monitors do not consume hourly monitor credits. A resumed monitor starts from the moment it resumes. It sends no event for a post made while it was paused.You cannot change the monitored
query. Delete this monitor and create another one to track a different query.Update handoff
Use this endpoint when a keyword alert changes scope or needs a temporary pause. Also use it when the alert must resume without creating a new monitor ID.Returned state
Store returned
id, query, eventTypes, isActive, createdAt, and
nextBillingAt. They are the current keyword monitor configuration.Event filter
eventTypes replaces the current filter. Keep
List Webhooks subscriptions aligned with the
monitor event types you expect to deliver.Pause monitoring
isActive: false pauses keyword polling, stored events, future webhook
deliveries, and hourly monitor billing. It applies to this monitor.Resume monitoring
isActive: true resumes polling for matching future tweets. Check
nextBillingAt, then run Test Webhook
before relying on production alerts. Posts made during the pause send no
event. Read them with Search Tweets.Query change
PATCH cannot change
query. Delete this monitor and create a new keyword
monitor. Do this when the X search query changes.Downstream join
After the update, keep using
keywordMonitorId and query from
List Events. Use them to reconcile stored
events and signed webhook payloads. Use
Get Event for one event’s full payload.Delivery audit
Use List Deliveries when you must
retain webhook delivery evidence. Join delivery
streamEventId to event
IDs. Do not use x_event_id as the delivery join key.Delete path
Use Delete Keyword Monitor only
when the query should stop permanently. Export event and delivery evidence
first when support or audit workflows need history.
Response
200 OK
string
Unique keyword monitor ID.
string
Normalized X search query.
string[]
Updated event types.
boolean
Current active status after update.
string
ISO 8601 creation timestamp.
string
Next hourly credit charge time for active monitor billing.
400 Invalid input
eventTypes values, or invalid isActive type.
401 Unauthenticated
404 Not found
429 Rate limited
Retry-After header before retrying.
Related.
- Get Keyword Monitor to verify state.
- Delete Keyword Monitor to remove it.
- List Events
- Get Event
- List Webhooks
- List Deliveries