Reddit Shuts Down Public Data API: September 30 Marks the First Deadline

By September 30, 2026, owners of applications using the Reddit Data API must re-register them. This is the first hard deadline in the plan that Reddit published on August 5 in the r/redditdev subreddit: the public Data API is being phased out, and third-party applications are moving to the closed Developer Platform (Devvit), where the code runs on the company's own servers. There is no announced date for the API shutdown — and this is what makes the situation unpleasant for everyone building anything on Reddit's data.

What was announced on August 5

The wording in the announcement is notably soft. Reddit promises to "gradually limit all new requests" to the public Data API and reassures users: "None of this is changing today. It honestly won't happen this year." — nothing is changing today, and it won't happen this year. Already approved OAuth keys continue to work, and new ones are issued, but through manual approval.

Behind this softness lies a change in architecture, not pricing. Devvit only supports JavaScript and TypeScript, the storage provides its own (Redis and blob-storage), and the code resides within Reddit's infrastructure. Python is mentioned separately and unequivocally in the announcement: "Python support is not currently on our roadmap." For a market where the overwhelming majority of data collection pipelines are written in Python using PRAW and requests, this is not a "migration," but a complete rewrite for a foreign runtime — with the loss of the right to keep data locally.

The calendar looks as follows:

• September 30, 2026 — the deadline for registering existing applications. Registration is free and does not obligate migration, but without it, the application will not be accounted for.
• December 31, 2026 — the deadline for completing migration for those who entered the Migration Program.
• There is no date for the Data API shutdown. A hard deadline has not been published — restrictions are being introduced "gradually."

The move is sweetened with money: Reddit has allocated about $1 million for the migration program, and individual developers receive a one-time payment of $1,000 after their application migrates and passes inspection. The selection criterion is that the application provides "substantial benefits or moderation features" to communities with an audience of at least 1,000 active users per week. This means the program is aimed at moderation bots, not analytical and research pipelines: if you are collecting Reddit data for market monitoring, product analytics, or model training, you do not fit into this funnel at all.

Timeline: why this does not seem unexpected

The announcement on August 5 is not a turnaround but the next step in a sequence that has been unfolding for three years.

1. July 2023 — the Data API becomes paid, with a rate of about $0.24 per 1,000 calls. Third-party clients are shut down.
2. End of 2025 — under the Responsible Builder Policy, self-registration of OAuth applications is canceled. Access is now requested via a support ticket, with waiting times measured in weeks, no SLA published, and denial being a common outcome.
3. August 2025 — Reddit blocks Wayback Machine indexing of post pages, comment threads, and profiles: the archive is left with almost only the main page. The reason given is that AI companies were scraping Reddit content through the archive. The technique is telling: there is no separate rule for the Internet Archive in robots.txt — it’s a blanket User-agent: * / Disallow: /, and the block is implemented at the infrastructure level.
4. May 28–30, 2026 — the oldest scraping endpoint dies: unauthenticated .json endpoints start returning 403.
5. June 2026 — Reddit closes old.reddit.com for non-logged-in users. A company administrator explained this directly: "Old Reddit's logged-out experience is a significant source of abusive scraping."
6. August 5, 2026 — the announcement of the phasing out of the public Data API.

Reddit speaks ambiguously about the old interface: "We don't have a hard timeline right now," and co-founder Steve Huffman described options as "limiting access, moving important scenarios, or rewriting from scratch." Meanwhile, AutoMod is being replaced by the LLM system Rules Hub — meaning moderation is also moving inside the platform.

A clear picture emerges: Reddit is methodically closing every entry point through which content was freely distributed, while simultaneously selling the same content under license — public deals with Google and OpenAI confirm this. The legal front is working in the same direction: on July 31, 2026, federal judge Paul Engelmayer in Manhattan largely denied a motion to dismiss Reddit's lawsuit against Perplexity, SerpApi, Oxylabs, and AWMProxy — the company accuses them of scheming to obtain its data bypassing direct access, through Google search results. A separate lawsuit by Reddit against Google itself was dismissed ten days earlier, on July 20. The dispute is precisely about whether obtaining public content through an intermediary constitutes a circumvention of protections — and so far, the court leans toward the view that this question deserves substantive examination.

What remains for those collecting Reddit data

Realistically: there is no longer any free official way to access Reddit data. Four routes remain, each with a clear price.

1. Register an application by September 30. If you have a working OAuth application, this is the cheapest thing to do rather than not do it. Registration is free and does not obligate you to anything, but not being in the registry is a poor position when the "gradual restrictions" reach your client. Approved keys are still operational, with a cap of 100 requests per minute per OAuth client ID, calculated as an average over a rolling ten-minute window. In practice, it consistently holds around 60 requests per minute: the rest are consumed by spikes. Monitor the headers X-Ratelimit-Used, X-Ratelimit-Remaining, and X-Ratelimit-Reset — this is the only feedback you have.

2. Devvit — if your product lives within Reddit. A moderation bot, a tool for a subreddit, an interactive post — yes, this has a place there, and they will even pay for the move. Analytics that need to export data externally have no place there: code on foreign servers does not give you your own copy of the data.

3. Commercial license. Direct negotiations, tangible money, working results. For a corporate task with a budget — the most predictable option, and the only one that won't break with the next announcement.

4. Historical archives. For retrospective analysis, the official API is often not needed at all. Pushshift has been available only to moderators since May 2023, but its successor Arctic Shift has revamped the archive and makes it publicly available: about 2.5 billion items (approximately 1.3 billion comments and 1.3 billion posts), 261.8 GB of compressed Parquet, with data updated to February 2026, and monthly releases. PullPush replicates the Pushshift endpoint scheme with a cap of about 1,000 requests per hour and is known for regular downtimes. For offline analysis, there is a 3.97 TB dump on Academic Torrents — without a search API, only for download. If your task is to "count what was discussed in 2019–2025," the archive fully covers it without risk.

Where the boundary of proxy responsibility lies

In such news, there is always the temptation to propose a simple solution: since the official channel is closed — take a pool of addresses and scrape as before. This is fundamentally incorrect, and it is worth clarifying the boundary directly.

Proxies solve accessibility and distribution tasks: bypassing regional restrictions, not hitting a limit on a single outgoing address when legitimately collecting public pages in parallel, checking how the output looks from another country, and managing independent working sessions. Residential addresses are needed where the target filters out datacenter ranges; datacenter proxies are cheaper and faster where such filtering does not exist.

What proxies do not do is provide authorization. No address turns a 403 on a closed endpoint into a 200, replaces an OAuth key, or lifts the restrictions of the platform's user agreement. Reddit closes access not by IP, but by access rights — and changing IP in such a situation is technically meaningless and legally risky, especially in light of the active lawsuit against four companies simultaneously. We discussed this logic in more detail in our article on when to choose the official API, when a dataset, and when scraping, and the practice of working with Reddit limits in our guide to collecting Reddit data.

What to do this week

If Reddit data is part of your product, there are less than three weeks left until September 30. A reasonable minimum:

• Conduct an inventory. Find all places where the code interacts with Reddit: OAuth applications, forgotten scripts on .json, third-party intermediary services. Scripts on .json are already dead — if any of them silently return nothing, you just haven't noticed it yet.
• Register working applications. Free, without obligations, and it removes the question of "what if."
• Separate tasks into historical and operational. Everything that can be counted from the archive should be moved to Arctic Shift — this part will no longer depend on Reddit's decisions at all.
• Assess what will remain without real-time access. If the product loses meaning without fresh data, consider the cost of a license now, not in December.
• Build in a buffer for limits. Plan a pipeline of 60 requests per minute, not 100: averaging over a ten-minute window means spikes consume the rest.

Conclusion

Reddit is not "killing the API" in one day — it is stretching the closure so that teams have no reason to panic today, and by the time real restrictions arrive, no alternatives will remain. September 30 is the only precise date in this plan, and it is free: not taking advantage of it would be strange. Everything else boils down to an honest question that is better answered in September than in December: how much is Reddit data worth to your specific product, and are you willing to pay for it — in time for rewriting for Devvit, in money for a license, or by giving up real-time access in favor of the archive.