Monitoring

Choose event types for an account

PATCH /v1/monitor/targets/{target} targets:write

Change which event types are delivered for an account you monitor, or for one still being resolved. The choice applies to the stream, webhooks and GET /v1/events alike; widen it again and the added types reach you from then on. An open connection picks the change up on its next refresh. Send If-Match with the ETag from the detail endpoint to avoid overwriting a concurrent change. Every type you can choose and common combinations: Choosing event types. {target} names the account: its user id, its current handle, or a handle it had before.

Request body

Body field	Type	Meaning
`event_types` *	string[] \| null	The event types to deliver, from `GET /v1/meta/event-types`; `null` or `[]` for every type

response

200 with the updated Target (or pending shape); 400 invalid_request naming unknown types in details.unknown; 404 not_subscribed; 412 when If-Match is stale. Field by field: Target.

Status: 200, 400, 404, 412

request

curl -X PATCH https://api.xsignalfeed.com/v1/monitor/targets/elonmusk \
  -H "Authorization: Bearer xsf_your_key" -H "Content-Type: application/json" \
  -d '{"event_types": ["tweet.create", "followers.verified.add"]}'

response · 200 / 400

{
  "target": {
    "id": "44196397",
    "screen_name": "elonmusk",
    "name": "Elon Musk",
    "previous_screen_names": [],
    "push_ready": true,
    "last_push_at": "2026-09-16T08:12:03.417000+00:00",
    "last_poll_at": "2026-09-16T08:12:10.002000+00:00",
    "state": "subscribed",
    "event_types": [
      "tweet.create",
      "followers.verified.add"
    ],
    "event_types_all": false
  }
}