What are the Reddit API rate limits?

The official Reddit API rate limit

On the official Reddit API, the free OAuth tier is capped at roughly 100 queries per minute and is licensed for non-commercial use only. To use it commercially you file an application, wait through a 2 to 4 week review, and move to enterprise pricing. That is fine for a research script but a real bottleneck for a product that needs predictable throughput on day one.

The official API surfaces the quota on every response rather than leaving you to guess where you stand. Three headers ride along with each call: how many requests are used in the current window, how many remain, and how many seconds until the window resets. A client that ignores all three finds out it is throttled from a 429, which is the expensive way to learn something the headers already told you a request earlier. A client that reads them can slow down before the wall rather than after hitting it, but that discipline is still work you have to build and maintain against a moving quota.

How Redditapis handles throughput

Redditapis is pay-per-call, so throughput scales with usage rather than a fixed free-tier cap. A read is $0.002, which means 10,000 reads is $20, and you are not held to the 100 QPM non-commercial limit. You can start with $0.50 in credits, about 250 reads, before adding a card. See the full breakdown on how much the Reddit API costs and the tiers on the pricing page.

Put a QPM number on that to make the comparison concrete. The official free tier caps a sustained job at 100 calls a minute no matter what you are willing to spend. On Redditapis, a job that needs 500 calls a minute for an hour is 30,000 reads, $60, and nothing else stands between the request and the response: no queue, no quota reset to wait out, no second application to file because the first job outgrew the free tier. The number that changes is the invoice, not a throttle you have to design around, and that invoice is one you can see and set a budget against before the job ever runs.

So what actually limits you here

Saying there is no QPM cap invites the obvious next question, which is what stops you instead. Three things, and none of them is a quota you have to apply for. Two are ordinary operating limits you can plan around before you write the job, and the third only ever shows up when something in your own code is wrong.

The first is your balance. Calls are billed as they are made, so the real ceiling on a burst is how much credit is sitting on the account. That is a number you control and can change in a minute, which is the difference that matters when a job needs to run tonight rather than after a review. There is no separate step to raise it: adding credit and the next call landing at full speed are the same action, not a request that waits on anyone.

The second is Reddit itself. Reddit still throttles the accounts any provider reads through, and we absorb that behind a pool rather than passing it to you as a quota. When the pool is momentarily out of capacity the call fails and is booked at $0, so a busy moment upstream costs you a retry rather than money. The pool exists specifically so that one customer's burst does not become another customer's throttle, which is the part a single shared account could never do.

The third only ever bites a bug. Requests to a path that does not exist are burst limited per key and also booked at $0, which means a typo in a route name cannot run up a bill while you are still wiring things together. It is the one limit on this list that is not really about throughput at all, it is a guardrail against paying for your own mistake while you debug it.

The two ceilings, side by side

The practical consequence is how you plan capacity. Against a QPM quota you design the job around the quota, spreading work across a window you did not choose. Against a balance you design the job around the work and then fund it, which is the same calculation as any other line in a build.

Commercial Access

The 100 QPM cap only describes the free, non-commercial tier. Reaching commercial access on the official Reddit API is a separate track entirely, gated by an application rather than a self-serve upgrade, and it runs on Reddit's timeline rather than yours.

Redditapis skips every one of those four steps. There is no application to file, no terms negotiation ahead of the first call, and no enterprise quote to wait on: the same bearer token that reads data for testing is the one a commercial product ships with, and it works from the first call rather than after an approval. The tradeoff runs the other way too: the official commercial track eventually buys direct, higher-volume access under Reddit's own terms, which is a real difference for a team that specifically needs that relationship rather than a proxy in front of it.

Which one actually matters depends on what the product does, not on which is theoretically bigger. A launch that needs to ship this quarter cannot spend three or four weeks waiting on an application before writing a line of code, and a team in that position is choosing between shipping and not shipping, not between two supported paths. A team that already has an enterprise relationship with Reddit, or one whose product requires attribution and terms only the direct commercial track grants, is optimizing for a different variable, and the review timeline is a cost worth paying once rather than a blocker every sprint. Most teams evaluating this question are the first kind: they know roughly what the product needs to do and want to be building it today, and a pay-per-call key that works immediately is the more direct route to that.

Best Practices and Considerations

Removing the QPM cap does not remove the reasons to be deliberate about how often you call. Every read still costs money, and the habits that made sense under a free-tier quota mostly still save you something under pay-per-call, just for a different reason: spend, not throttling.

None of this is about avoiding a throttle response, because there is not one to avoid. It is the same discipline any metered API rewards: read once and reuse what does not change, push instead of poll where a push exists, and treat the credit balance as the operational number worth alerting on, the way a QPM dashboard would have been under the official tier.

Frequently asked