Feature Request: Add Retry-After and X-RateLimit-Remaining Headers to API Responses

 

Our development team would like to formally request the addition of Retry-After and X-RateLimit-Remaining  headers to the OwnerRez API responses. Adding these headers would provide essential data for our client-side traffic management.
Justification for the Headers:

• Improved Rate-Limit Management: We are actively implementing an outbound rate-limit governor on our HTTP client to ensure our traffic stays below the cap with necessary headroom.
• Clean Recovery from Errors: Currently, when a 429 "Too Many Requests" error is received, the client has to rely on guesswork for retry timing. Providing the Retry-After header would allow us to implement "better retry/backoff on the queue side" so that any 429 errors we see "recovers cleanly".
• Fine-Tuning: The X-RateLimit-Remaining header would allow us to fine-tune our client-side governor, giving us real-time insight into the available capacity before we hit the limit.

Implementing these standard rate-limiting headers would significantly improve the robustness and efficiency of our HomeRunner integration, leading to a better experience for the OwnerRez customers we both support.