API Enhancement Request – Include Email Profile Count in List API Response

Hi Klaviyo Team,

I’ve been reviewing the current Developer API documentation and noticed that the /lists/{list_id}/profilesendpoint does not return the total count of email profiles associated with the list.

For example, my list with ID VAZemD contains 10 profiles. However, when calling the following API:
curl --location 'https://a.klaviyo.com/api/lists/VAZemD/profiles' \
--header 'Authorization: Klaviyo-API-Key xyzkey' \
--header 'Accept: application/json' \
--header 'Revision: 2025-01-15'

The response does not include the profile count.

This is a standard feature provided by other platforms such as Mailchimp, Google Contacts, and HubSpot. Having the profile count readily available is crucial when building integrations, reporting usage, or simply understanding list sizes at a glance.

While it’s technically possible to create a segment and then query the count, this adds unnecessary overhead—multiple steps for what should be a simple, single-call operation. End users expect quick access to such basic information without the extra complexity of segment creation.

Given Klaviyo's rapid growth and focus on developer experience, I believe including the email profile count directly in the list API response would be a valuable and expected improvement.

Thanks for considering this enhancement.

Best regards,
Gourav Gupta

Page 1 / 1

Hi @Devphoenix ,

Thank you for reaching out to the Community! In order to include profile count in your API call, you will need to use our singular Get List endpoint (rather than ‘Get Lists’ or ‘Get Profiles for List’). When building this you will just need to request an additional field with the value ‘profile_count’:

I hope this solves the issue, and let me know if you have any additional questions!

Thanks @emma.owens !!

curl --location --globoff 'https://a.klaviyo.com/api/lists/VAZemD?additional-fieldselist]=profile_count' \
--header 'Authorization: Klaviyo-API-Key xyz' \
--header 'accept: application/vnd.api+json' \
--header 'revision: 2025-04-15'

But why do we need to pass it, also it leads to miss the contact information which are coming previously with `/lists/{list_id}/profiles`

@Devphoenix Yes, this call is different from the ‘Get Profiles for List’ endpoint, which includes all of the contact information of each profile!

@emma.owens
As a best practice for integration API design, don’t you think including a count in the "Get Profiles for List" response would be a more effective solution? Platforms like HubSpot and Mailchimp already follow this approach, making it easier to manage and validate data.

Hi @Devphoenix !

I can definitely see why this would be useful rather than having to make multiple calls, so I have gone ahead and submitted a product feature request for this so hopefully we can implement a solution in the future!

Thanks @emma

I hope this will improve Klaviyo API performance.

Sign up

Use your Klaviyo credentials

Log in to the Community

Use your Klaviyo credentials

Scanning file for viruses.

This file cannot be downloaded