Skip to main content
Solved

Unexpected Values in V2 API Rate Limit Headers

  • Dec 16, 2024 3:45 AM UTC
  • 1 reply
  • 463 views

Forum|alt.badge.img+4

Hello,

I have a question regarding the V2 API.

When I make a single API call(`/subscriptions`), the value of RevenueCat-Rate-Limit-Current-Usage in the response headers appears something weird. For instance, I receive values like 686 or 602 for a few calls, while RevenueCat-Rate-Limit-Current-Limit is set to 480.

The Current-Usage value is higher than the Current-Limit, yet no rate limiting is applied.

Could you explain the logic behind how these values are determined?

Or is trial and error until the rate limit is triggered the best approach to understand this?

Best answer by antonio

Hi ​@heejin-lee-cf2117 ,

 

Thank you for reporting. This was a bug and should be now fixed. Let us know if you still see issues with the rate limit headers. 

View original
This post has been closed for comments

1 reply

antonio
RevenueCat Staff
Forum|alt.badge.img+4
  • RevenueCat Staff
  • Answer
  • Dec 17, 2024 12:53 PM UTC

Hi ​@heejin-lee-cf2117 ,

 

Thank you for reporting. This was a bug and should be now fixed. Let us know if you still see issues with the rate limit headers.