X write
Twitter mute API to mute an X user by user ID
Mute 1 X user by ID from a connected X account. Store the write action, terminal result and billed credits. Retry only when safeToRetry is true. 10 credits.
- 200
- 202
- 400
- 401
- 402
- 403
- 404
- 409
- 422
- 429
- 500
- 503
POST
Twitter mute API to mute an X user by user ID
10 credits per call · All plans from $0.00012/credit
Mute one user by ID
Put the exact user ID in the request path. Put the connected account username or ID in the body. That account mutes the user. The user’s posts leave that account’s home timeline. The user can still follow, reply and mention the account. Use Unmute user to reverse a mute.Save a receipt
Save the action first. Then update your local record.Handle errors
Never infer failure from a client timeout. Poll a returned action before sending another request.- For
400, correct the user ID or account value. - For
401, replace invalid Xquik authentication. - For
402, add credits before another request. - For
403, reconnect the selected X account. - For
409, keep the original action and payload. - For
422, review the X rejection before retrying. - For
429, wait forRetry-After. - For
500or503, followsafeToRetryandterminal.
Headers
string
Send your Xquik API key in this header. Alternatively, send an OAuth 2.1 bearer token.
string
Send
Bearer <token> instead of x-api-key when using OAuth 2.1.string
required
Unique key for this intended write. Reuse it only for an exact network replay.
string
required
Must be
application/json.Path parameters
string
required
User to mute. Send a user ID or a username with or without
@. A URL-encoded profile URL such as x.com/nasa also works.
An unknown username returns 422 x_target_not_found. See path IDs.Body
string
required
X username or account ID identifying which connected X account acts. Xquik strips the
@ prefix if included.Response
Durable write recovery
- Store
id, the nestedhashinrequest,billing, andstatusUrl. - Poll after
Retry-AfterorpollAfterMswhenterminalisfalse. - Retry only when
safeToRetryistrue. - Use a new key when
nextAction.requiresNewIdempotencyKeyistrue.
200 terminal or 202 active
- After HTTP
200, store the result and settled billing. - After HTTP
202, poll the same action. Never submit another write. - After HTTP
400, fix the named field. Use a new idempotency key. - After HTTP
401, fix authentication. Do not retry unchanged. - After HTTP
402, fund the account before another write. - After HTTP
403, reconnect the account. - After HTTP
409, keep the original action. Use a new key for new input. - After HTTP
422, fix the rejected request before retrying. - After HTTP
429, wait forRetry-After. FollownextAction.