Skip to main content
DELETE
Delete Tweet Drafts Safely with the Xquik API

Delete One Saved Tweet Draft

Delete one tweet draft from your Xquik account. The request removes its saved text, optional topic, optional goal, and timestamps. It does not publish the draft or call an X write route. This endpoint manages Xquik draft records only. It does not manage drafts under X’s native Unsent posts. It also does not delete published tweets, scheduled posts, or connected X accounts. Use the draft ID returned by Create Draft or List Drafts. Fetch the draft before deletion when its text must receive human approval.
Deletion is permanent. Xquik provides no restore endpoint for deleted tweet drafts. Confirm the saved text and draft ID before sending this request.
Free - does not consume credits

Handle 204 No Content

A successful tweet draft deletion returns 204 No Content. The response has no JSON, text, or deletion object. Check the status before parsing the body. Calling response.json() after a successful deletion throws an end-of-input error. Parse JSON only for 400, 401, 404, or 429 responses. The 204 status confirms that Xquik deleted the matching draft record. It does not return the deleted text. Fetch and store any needed review copy first.

Confirm the Correct Tweet Draft

Use a read-before-delete flow for dashboards, agents, and scheduled cleanup jobs.
  1. Fetch the draft through GET /drafts/{id}.
  2. Compare its id, text, topic, goal, and timestamps.
  3. Ask for confirmation when a person owns the draft.
  4. Send DELETE /drafts/{id} once.
  5. Accept only 204 as a successful deletion.
  6. Remove the draft from your local queue.
  7. List drafts again when reconciliation matters.
Do not guess draft IDs. Use an ID returned to the authenticated account. A numeric ID owned by another account returns 404 without exposing ownership.

Understand What Deletion Changes

A saved Xquik tweet draft is not a published tweet. It has an Xquik draft ID, not a public tweet ID. Deleting one cannot remove replies, reposts, likes, or media attached to a published post.

Recover From Draft Deletion Errors

A second deletion of the same ID returns 404. The first request already removed the record. Treat that result as already absent only when your workflow permits that interpretation. Never retry 400, 401, or 404 without changing the request. Retrying the same invalid input creates noise and cannot restore a deleted draft.

Answer Tweet Draft Deletion Questions

Does This Delete a Published Tweet?

No. This route deletes one saved Xquik draft. Use the documented tweet deletion route for a live post owned by the connected account.

Does This Delete My Native X Draft?

No. Native X drafts appear under Unsent posts. Xquik draft IDs identify separate records stored for API composition workflows.

Can I Restore a Deleted Tweet Draft?

No restore route exists. Save an approved copy before deletion when retention rules require one.

Can I Delete Every Draft in One Request?

No bulk deletion route exists. List drafts, confirm each target, and delete each ID separately. Apply your own concurrency and rate-limit controls.

Why Does a Successful Delete Return No JSON?

HTTP 204 means the deletion succeeded without response content. Check the status code instead of parsing a body.

Why Does a Retry Return 404?

The first successful request removed the draft. Later requests cannot find the same account-owned record.

Does Deleting a Draft Consume Credits?

No. This authenticated route is free and consumes no Xquik credits.

Path Parameters

string
required
The unique Xquik draft ID. Copy it from Create Draft or List Drafts.

Headers

string
Your Xquik API key. Generate one from the dashboard.
string
An OAuth bearer token formatted as Bearer YOUR_TOKEN. Send this header or x-api-key, not both.

Response

The draft was deleted. Do not parse a response body.
Related: List Drafts to verify the draft was removed, or Create Draft to save a new one.