Skip to main content
Solved

Unexpected Values in V2 API Rate Limit Headers

  • December 16, 2024
  • 1 reply
  • 53 views
H
Forum|alt.badge.img+2

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
Did this post help you find an answer to your question?
This post has been closed for comments

1 reply

antonio
RevenueCat Staff
Forum|alt.badge.img+4
  • antonio
  • RevenueCat Staff
  • 41 replies
  • Answer
  • December 17, 2024

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. 

H
1 person likes this
  • H
    heejin-lee-cf2117

Most helpful members this week

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings