---
title: "Rate limit headers missing from API responses"
url: "https://demo.myforumcat.com/q/99/rate-limit-headers-missing-from-api-responses"
forum: "Demo"
question_number: 99
category: "General"
tags: ["Imports", "Webhooks"]
status: "solved"
solved: true
votes: 5
replies: 7
views: 413
asked_at: "2026-07-26T01:23:35.928Z"
updated_at: "2026-09-18T22:18:50.393Z"
---

# Rate limit headers missing from API responses

Asked by Jane Cooper on 2026-07-26 · 5 votes

We do not see a remaining requests header in the response, which makes it hard to back off proactively.

## 7 replies

### Reply 1 (marked as the solution)

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

Confirmed gap, added an X-RateLimit-Remaining header to every API response in the next release so you can back off before hitting 429s instead of reacting to them.

### Reply 2

Kai Tanaka · 2026-07-26 · 1 vote

Looking forward to this, currently guessing at our remaining quota.

### Reply 3

Elena Marsh (Agent) · 2026-07-26 · 3 votes

Shipped this in the release right after the thread, should be live on every response now.

### Reply 4

Laura Simmons · 2026-07-26 · 1 vote

Great, this will let us back off proactively instead of guessing.

### Reply 5

Margaret Doyle · 2026-07-26 · 1 vote

Confirmed seeing the header on our latest requests, works as described.

### Reply 6

Ravi Patel · 2026-07-26 · 1 vote

Nice, this was the main thing blocking us from tightening our own retry logic.

### Reply 7

Sam Rivera (Agent) · 2026-07-26 · 2 votes · In reply to Reply 1

Also worth knowing the header reflects the per-key limit, not a per-tenant one, in case you have multiple keys.