I haven’t been able to find any endpoint where I can retrieve the count of subscribers to a given list or segment.
Trying to get a count from api/v2/group/LIST_OR_SEGMENT_ID/members/all would take too long and probably trip the rate limit with my list of 160K+ subscibers.
Seems like it would make sense to be included in the Get List Info call.
Quick update for everyone - the V3 API will give you the ability to pull the subscription status for all profiles in a given list or segment. We’re looking at a timeframe of Q4 22’ to Q1 23’ for this particular feature.
Thanks for being community members and making the community a place to share ideas and inspiration.
No profile_count at all. What might I be missing? I’m calling https://a.klaviyo.com/api/lists/YzT7bf/
And this profile_count should be added to the https://a.klaviyo.com/api/lists/ call too. I get all my lists, but I still have to loop through them all to get a profile_count.
If you’re not seeing the profile count it’s because you have to elect to include the additional-fields[list] Query Param for profile count when making the call. See the example here in the developer portal:
If you’re not seeing the profile count it’s because you have to elect to include the additional-fields[list] Query Param for profile count when making the call. See the example here in the developer portal:
Can I use this ?additional-fields[list]=profile_count on all the /lists/ listing too? Or do this only work on a single /lists/Yzt7bf/ type of thing?
Only on a single list
This is bad. Our customer allows us to view their lists/segments for our web app. We need to show the profile count for each. They have about 100 lists.
Rate limits when using the additional-fields[segment]=profile_count parameter in your API request:
Burst: 1/s
Steady: 15/m
So under the old API I could hit https://a.klaviyo.com/api/v1/lists... to get all the lists and a person_count was included. Great. It only took like 1 second to get 100 lists and their counts.
Now under the new V3 API I must separately call each /lists/xyzabc to get its profile_count. But the rate limit forces me to do this as low as 15 hits a minute.. so to list 100 lists + their counts now takes close to two minutes. The user just sits there waiting.
Absolutely ridiculous and makes our solution useless. Where it was great before. Why are you making things worse?
@Brian Turcotte Hello! I’m able to get the profile count on a list but when i try with the segment endpoint i get a 400. Isn’t it supposed to work with segments too?
Thanks!
EDIT: NVM, on the segments endpoint i had ?additional-fields[list]=profile_count. But should be ?additional-fields[segment]=profile_count. My bad 😁