Contributor I

Solved

API - Get count of subscribers in List or Segment

Forum|Forum|5 years ago
May 12, 2021
24 replies
1823 views

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.

Thank you

lists

Best answer by Dov

Hi @mkren47,

Thank you for sharing your feedback with the Klaviyo Community.

That is excellent feedback. I have submitted it as a proposal for our product team to consider implementing in the future.

In the meantime, I’d recommend exporting the list(s) and segment(s) in question through a .csv file as another way to retrieve both a subscriber count and all details pertaining to those profiles. Also, keep in mind that only Klaviyo users with the Owner, Admin, or Analyst roles have the ability to export lists and segments.

Thanks and have a wonderful Thursday.

Show previous replies

B

bproulx

Contributor IV

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

K

kenw232

Contributor IV

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?

B

bproulx

Contributor IV

@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 😁

C

cplowman

Contributor I

Potentially bumping this from the graveyard, but is there a solution here? My web app displays all lists and segments for a customer, and I need to provide just the profile_count for each. Is it really going to take 1s PER record to fetch that? That will take minutes of the user just staring at the screen?

Is there any way to include profile_count in the general /lists call?

Sign up

Use your Klaviyo credentials

Log in to the Community

Use your Klaviyo credentials