Compat: Remove User from Tweet Monitoring API

POST oapi/x_user_stream/remove_user_to_monitor_tweet removes a monitored user by translating an x_user_stream-shaped request onto DELETE /twitter/monitor/{id}. It takes one required parameter, id_for_user, which is the monitor id returned by GET /oapi/x_user_stream/get_user_to_monitor_tweet. It returns a status field (success or error) and a msg field with a human-readable result. The call costs 0 credits.

curl -X POST "https://example.com/oapi/x_user_stream/remove_user_to_monitor_tweet" \  -H "Content-Type: application/json" \  -d '{    "id_for_user": "b6f2c1a4-9e3d-4c11-8a2f-7d5e6c9b0a11"  }'

{  "status": "success",  "msg": "User removed from tweet monitoring."}

{  "error": "bad_request",  "message": "Missing or malformed parameter. Fix the request before retrying."}

{  "error": "unauthorized",  "message": "The API key is missing, malformed, or revoked. Check the Authorization header."}

{  "error": "insufficient_credits",  "message": "Your balance is exhausted. Top up your credits to continue."}

{  "error": "forbidden",  "message": "The acting account is not authorized for this write action, or has no logged-in session."}

{  "error": "not_found",  "message": "The resource does not exist, for example a deleted tweet or a private account."}

{  "error": "rate_limited",  "message": "Too many requests. Back off and retry with exponential backoff."}

{  "error": "server_error",  "message": "Something failed on our side. Retry with backoff; if it persists, contact support."}

Pricing

When to use

Use this endpoint only if your integration was originally built against x_user_stream's remove-user request/response shape and you want to keep that envelope while removing a monitor. If you are building fresh, call DELETE /twitter/monitor/{id} directly instead of this compatibility wrapper.

Notes

• 404 with an error status if the id_for_user does not exist or belongs to a different API key.
• Irreversible, same as DELETE /twitter/monitor/{id}: there is no undelete.
• Lives at /oapi/x_user_stream/..., not under /twitter/ -- match the base URL in the example exactly.

Related endpoints

• Create Monitor: Watch an X account for new posts and push them to your webhook(s).
• List Monitors: List every monitor on your account.

FAQ

Where do I get the value to pass as id_for_user?

Call GET /oapi/x_user_stream/get_user_to_monitor_tweet first and read the monitor id from its response. id_for_user is exactly our internal monitor id, not the monitored user's Twitter/X user ID, so passing a raw Twitter user ID will not match.

Does removing a monitor here cost credits, and how do I know it worked?

The endpoint costs 0. Check the status field in the response: success means the monitor was deleted, error means it was not, and msg carries the human-readable detail for either outcome.