Open a new issue

We need a new issue to track adding a rate limit header to all API responses. Open the issue assigned to Priya, describe the desired behavior, include the API endpoints affected, set the priority to high, assign it to the backend team, and add the labels api, enhancement, and needs-design.

Before I open this issue about adding rate-limit headers, make it easy for the backend lead to approve: put the expected header name and value format up top, list the endpoints and client libraries that must be changed, estimate the scope as a small or medium task, and call out any compatibility risks that would make a reviewer hesitate.

We’re ready to add rate-limit headers but the team is split between using X-RateLimit-Remaining and a single RateLimit header with JSON. I don’t know which format clients expect and am worried about breaking mobile SDKs. What is the likely better choice and the least risky next step to decide, given we can run a short compatibility check with the three top SDK owners?

Across many repos we spend time debating scope because new issues lack consistent endpoint lists, expected behaviors, and impact estimates. Which habit change will reduce back-and-forth and speed implementation across teams: a stricter issue template, a pre-issue checklist, or mandatory triage meetings? Recommend one change and a one-sentence enforcement rule for PRs or issues.