Rate Limit of legacy API (track and identify) vs new API

Question

Hey everyone!We are migrating from v1/v2 to new API.We were using the track and identify endpoints, and now shifted to event /profile.The new API documentation indicates a rate limit (e.g. Burst: 350/s, Steady: 3500/m), but I don’t find in the legacy documentation what it’s rate limit was.I want to understand if the new API is stiffer or lighter?

saulblum · Accepted Answer

The legacy /track and /identify calls don’t have any published rate limits. They’re asynchronous, and return just 1 or 0.

If you need to process more profiles and events, there are bulk calls:

https://developers.klaviyo.com/en/reference/spawn_bulk_profile_import_job

https://developers.klaviyo.com/en/reference/bulk_create_events

There’s also SFTP for bulk import: https://developers.klaviyo.com/en/docs/use_klaviyos_sftp_import_tool

KeviSunshine · Answer

Hi @AW1,I’m under the impression that the new endpoints are stiffer. The old endpoints did not have rate limits documented, but all of the new endpoints have them. This makes me think they were added with the V2 versions.But I’m curious!Best,Kevin.

Sign up

Use your Klaviyo credentials

Log in to the Community

Use your Klaviyo credentials