"As a Client Developer, I want to have informational HTTP headers in my response that say what my rate limit is and how many requests I still have available, so that I can throttle my requests to avoid going over the limit."
Different services use different proprietary headers for rate-limit information. We can use those, define our own, or use the draft RFC for rate-limit headers from the IETF.
Note that this is for successful and error messages.
This is done when:
- Our responses follow the RFC for rate limit headers
- Every response has rate limit in the headers (somewhere) or we know why not
- Every response has remaining calls in the headers (somewhere) or we know why not
- Every response has reset time in the headers (somewhere) or we know why not