Solved

Replacement for v1/v2 {list_or_segment_id}/members/all in new API

  • 27 March 2024
  • 2 replies
  • 30 views

Badge

Hi!

We are currently using this endpoint to get all members of a list and segment “pretty” fast cause each request returns up to 1000 profiles with Email and Phone Number.

Now when this gets deprecated, we are very limited to this functionality, since in our own Web-App we are syncing the lists/segments from klaviyo to our CRM. When I use alternative endpoints, with only max. 100 profiles returned, the sync for a segment/list takes 10x the current time, which is already long (approx. 5 minutes for segment > 30k)

Does someone have a solution for this? Or any tips on how I can improve on my end? 

icon

Best answer by KeviSunshine 27 March 2024, 12:00

View original

2 replies

Userlevel 4
Badge +7

Hi @chatarmin,

We have a similar use case (fetching all profiles in a segment), and we concluded that the `/segments/{segmentId}/profiles` and fetching 100 at a time was the best solution.

We run ours in a recursive loop and it takes about 10 seconds for every 2,000 records. I would expect 30,000 records to take about 2.5-3 minutes. 

I don’t have a solution for you, but I wanted to share my experience.

 

Best,

Kevin.

 

Badge

Thanks very much! I am now using those endpoints too in a recursive loop. Thanks!

Reply