API limits changed?

Forum|Forum|2 years ago
February 6, 2024
3 replies
168 views

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?

This topic has been closed for replies.

Best answer by saulblum

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

S

saulblumAnswer

Klaviyo Employee

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

B

babisAuthor

Contributor III

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.

Brian Turcotte

Klaviyo Alum

Hi @babis!

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

Best,

Brian

Sign up

Use your Klaviyo credentials

Log in to the Community

Use your Klaviyo credentials