X Write
How to Delete a Community on Twitter via API
Delete an owned X community by ID and confirmed name. Archive its tweets, members, moderators, and rules, then verify the final write lifecycle state.
- 200
- 202
- 400
- 401
- 402
- 403
- 404
- 409
- 422
- 429
- 500
- 503
DELETE
How to Delete a Community on Twitter via API
How to Delete a Twitter Community Through REST
CallDELETE /x/communities/{id} for one community owned by a connected
account. Send its exact community_name as a confirmation safeguard. This
route removes the community, not the connected X account.
This route explains how to delete a Twitter Community through one tracked
deletion action. It also shows how to delete Twitter Community records safely.
Use Leave Community to remove one
account’s membership. Use Delete Tweet
to remove one owned Community post.
10 credits per call · All plans from $0.00012/credit
How to Delete Twitter Community Records Safely
Confirm the community ID, owner, exact name, reason, and approver. Create oneIdempotency-Key for that deletion. Reuse it only during unchanged network
recovery. Xquik has no restore route. Plan for permanent removal.
Archive required records before approval:
- Save the name, description, rules, creator, and policies from Community Info.
- Follow every Community Tweets cursor. Store tweet IDs, authors, text, timestamps, media URLs, replies, reposts, and likes.
- Follow every Community Members cursor. Store stable user IDs and the final
hasMorevalue. - Export Community Moderators separately. Member rows do not prove moderator roles.
Verify Permanent Community Deletion
Store the action ID after200 or 202. Poll while terminal is false.
After terminal success, call Community Info.
An unavailable community confirms removal. A temporary read failure does not.
Repeat the read before starting another deletion.
Fix Twitter Community Deletion Errors
Fix invalid fields after400. Replace credentials after 401. Add credits
after 402. Reconnect the owner after 403. Verify the account and community
after 404. Resolve key conflicts after 409. Review rejected requests after
422. Honor Retry-After after 429. Check safeToRetry after 500 or 503.
Delete Twitter Community Questions
Can You Delete a Twitter Community?
Yes. Send the community ID and exact name through the connected owner. Xquik then returns a tracked write action.Does Deletion Affect the Owner’s X Profile?
No profile field appears in the request body. The route targets one community ID. It does not disconnect or delete the owner’s X account.Can a Deleted Community Be Restored?
Xquik documents no restore endpoint. Archive first and treat deletion as permanent within this API workflow.Can I Transfer Ownership Instead?
This route has no ownership-transfer field. Complete any supported transfer in X before deletion, then verify the intended owner.What Happens to Members and Community Posts?
Members lose access to the deleted Community. X says existing Community posts are not deleted with the Community. Archive required posts before removal. Use Delete Tweet for an owned post.Headers
string
required
Your API key. OAuth bearer authentication is also supported. Generate a key from the dashboard.
string
required
Unique key for this intended write. Reuse it only when every field remains unchanged after interruption.
string
required
Must be
application/json.Path parameters
string
required
The ID of the community to delete.
Body
string
required
The connected X account that owns the community. Must be a username you have connected to your Xquik account.
string
required
The exact community name. Send it to avoid deleting a different Community.
Response
- 404 Account Not Found
Connect the requested account, then submit a newly approved write.
Durable Write Recovery
- Store
id, the nestedhashinrequest,billing, andstatusUrl. - Poll after
Retry-AfterorpollAfterMswhenterminalisfalse. - Trust
safeToRetryandnextActionbefore any new write.
200 Terminal or 202 Active
Store terminal results. Poll active actions without creating another write.- 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. Preserve the same key. - After HTTP
500, retry only whensafeToRetryistrue. - After HTTP
503, poll whileterminalisfalse.
- 200
- 202
- 400
- 401
- 402
- 403
- 404
- 409
- 422
- 429
- 500
- 503
How to Delete a Community on Twitter via API