DELETE https://xquik.com/api/v1/x/dm/{userId}/messages/{messageId}
10 credits per deleted DM · Compare plansA write that must sign in to your X account first adds 10 credits. Xquik refunds them if the sign-in fails. A sign-in that works keeps them, even if X then refuses the write. See the X sign-in fee.
Delete a direct message with the Twitter DM API
This route deletes 1 DM from the connected account’s side of the conversation. The other person still sees it. Xquik charges 10 credits only when X deletes the DM. Put the other person in the path and the DM ID inmessageId.
DM history and Send DM return DM IDs.
Send your connected account in the account query parameter.Confirm the delete
Xquik confirms the DM is deleted before it reports success. A200 response means the DM is gone.
Its result has type: "state_change", the DM id and state: "deleted".
A 202 response means Xquik has not confirmed the delete yet.
Poll statusUrl until terminal is true.
You pay nothing while the delete is pending.
Deleting the same DM again also succeeds.Handle delete DM errors
400 invalid_message_idmeansmessageIdis not a DM ID. Copy it from DM history.400 account_requiredmeans theaccountquery parameter is missing.404 account_not_foundmeans the account is not connected to Xquik.422 x_dm_not_deletedmeans X still shows the DM. You pay nothing, andsafeToRetryistrue.
Headers
Path parameters
Query parameters
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.
Response examples
200 example
202 example
- 400
{ "error": "missing_idempotency_key", "message": "Idempotency-Key is required. Generate one unique key for this write.", "charged": false, "chargedCredits": "0", "retryable": false, "safeToRetry": true } - 401
{ "error": "unauthenticated", "message": "Authentication required. Provide a valid API key or bearer token." } - 402
{ "error": "insufficient_credits", "message": "Insufficient credits. Top up or subscribe to continue." } - 403
{ "error": "api_key_paused", "message": "This API key is paused. Resume it at dashboard.xquik.com/api-keys to use it again." } - 404
{ "error": "account_not_found", "message": "X account not found. Connect it first at /dashboard/x-accounts." } - 409
{ "error": "idempotency_conflict", "message": "Idempotency-Key was already used with a different request.", "charged": false, "chargedCredits": "0", "retryable": false, "safeToRetry": true } - 422
{ "error": "x_rejected", "message": "X rejected this request. Check what you sent & the account on x.com before you try again." } - 429
{ "error": "rate_limit_exceeded", "message": "Too many requests. Try again later.", "retryAfter": 60 } - 500
{ "error": "x_write_failed", "message": "Write action failed unexpectedly. Contact support if this persists." } - 503
{ "error": "write_tracking_unavailable", "message": "Write tracking unavailable. Try again.", "charged": false, "chargedCredits": "0", "retryable": true, "safeToRetry": true }