--
title: "Why X Rate Limits Slow Down Bulk Deletion: Quotas and Queueing"
description: "Bulk deletion is slow for one reason: how write quotas are counted inside a rolling window. Understand the window, the per-endpoint split and what a 429 actually means, and the job becomes a queue you control."
tags: ["api", "twitter", "privacy", "webdev"]
canonical_url: https://digital-footprint-health.shop/blog/x-api-rate-limits-deletion
Why X Rate Limits Slow Down Bulk Deletion: Quotas and Queueing
Bulk deletion is slow for one reason: how write quotas are counted inside a rolling window. Understand the window, the per-endpoint split and what a 429 actually means, and the job becomes a queue you control.
The short version first, then the part that usually gets skipped.
Deletion is a write, and writes draw from a far tighter allowance than reads. A timeline that scrolls instantly says nothing about how fast you can remove posts, because the two operations spend from different quotas. Treating them as one budget is what produces the surprise.
What actually works, in order: Survey with the read channel and let the write channel only execute. Split the total into fixed-interval segments with gaps between them, keep one log line per segment, and resume from the last confirmed count rather than starting the run again.
The numbers worth knowing: Allowance refills on a sliding window, so a short pause plus one probe request usually tells you whether to resume. For accounts past a thousand posts, measuring locally first typically cuts the actual deletion volume to under a third of the timeline.
Where people go wrong: Retrying immediately after a 429. The platform reads rapid retries as sustained high frequency and answers with a longer restriction window, so the aggressive retry makes the pause worse than the original limit.
A note on defaults. Every tool in this space ships with settings chosen for the average case, and if your situation is not average, the default path is what sends you back to redo the work a month later. Decide what you are optimising for in one sentence, then let that sentence filter the steps. Anything that does not connect to it can wait.
I keep the full walkthrough with the order of operations on my own site, here: https://digital-footprint-health.shop/blog/x-api-rate-limits-deletion
Top comments (0)