---
title: "Separate rate limits for read and write endpoints"
url: "https://demo.myforumcat.com/q/100/separate-rate-limits-for-read-and-write-endpoints"
forum: "Demo"
question_number: 100
category: "General"
tags: ["Localization", "SSO"]
status: "solved"
solved: true
votes: 12
replies: 6
views: 220
asked_at: "2026-07-26T08:11:27.100Z"
updated_at: "2026-09-18T22:19:28.494Z"
---

# Separate rate limits for read and write endpoints

Asked by Marcus Lee on 2026-07-26 · 12 votes

Are GET requests rate limited separately from POST and PATCH, or do they share the same bucket?

## 6 replies

### Reply 1 (marked as the solution)

meow (Owner) · 2026-07-26 · 3 votes

Same bucket today, GET and POST both draw from the same per-key limit, writes just tend to be heavier in practice. Splitting them is on the list but not scheduled yet.

### Reply 2

Margaret Doyle · 2026-07-26 · 1 vote

Makes sense, our write-heavy sync job was the one hitting limits first.

### Reply 3

Mei Lin · 2026-07-26 · 1 vote

Would still like to see them split eventually, our read traffic is much higher than writes.

### Reply 4

Peter Novak · 2026-07-26 · 1 vote

Makes sense, we adjusted our sync job to batch writes more aggressively in the meantime.

### Reply 5

Mei Lin · 2026-07-26 · 1 vote

Would still like this split eventually but understand it is not urgent for most tenants.

### Reply 6

Daniel Brooks (Admin) · 2026-07-26 · 1 vote · In reply to Reply 1

Agreed this is lower priority than some of the other API work in flight, but it is on our radar.