Solved

API limits changed?

  • 6 February 2024
  • 3 replies
  • 56 views

Userlevel 1
Badge +1

Since today, we are noticing values for the RateLimit–Limit header for rate limits that are not listed here: https://developers.klaviyo.com/en/docs/rate_limits_and_error_handling#rate-limits

Some of those header values:

'10, 10;w=1, 150;w=60'
'75, 75;w=1, 700;w=60'

Until now we were able to match and use those values instead:

'150, 10;w=1, 150;w=60'
'700, 75;w=1, 700;w=60'

Is this a change on purpose, on the current API stable version v2023-12-15? Should we expect new header values now? Or they are on top of the existing values, and how should we translate them?

icon

Best answer by saulblum 6 February 2024, 20:04

View original

3 replies

Userlevel 4
Badge +7

There was an update to make the header reflect the actual enforced limits, if certain additional parameters are used. For example, for Get Profiles:

Rate limits when using the additional-fields[profile]=predictive_analytics parameter in your API request:
Burst: 10/s
Steady: 150/m

Userlevel 1
Badge +1

Should those updates happen on a new API version and the docs be updated, rather than breaking existing API version that may be used in a production system? Thank you.

Userlevel 7
Badge +36

Hi @babis!

I will reach out to our documentation team to have those updates reflected immediately.

 

Best,

Brian

Reply