Improve your GET PROFILE API

Just want to say that I agree with this. Adding a total number of pages to the standard `links` response object for all paginated endpoints would be a good improvement!

The easiest way to do this right now would be to make a segment that contains all profiles — e.g. defined as, “email or phone number exists” — and then call Get Segment (https://developers.klaviyo.com/en/reference/get_segment).

The response includes a profile_count property.

Thanks for your response. However, don’t you think it would be more logical and aligned with business use cases to include the total profile count directly within the GET Profile API? Many other platforms like Google, HubSpot, Mailchimp, etc., provide this information as a primary feature without any second thoughts. Requesting a simple count shouldn’t be overly complex.

Creating a segment to achieve this functionality doesn’t seem practical, as not all users would prefer to create segments just to retrieve a count. If I only need the total profile count, creating a segment feels like an unnecessary step.

As Klaviyo is a platform designed to cater to diverse needs, I would expect this feature to be inherently available.

Thanks for considering this suggestion!

I recommend implementing meaningful pagination links in the API navigation rather than using tokens. This enhancement will enable developers to easily navigate to a specific page number, streamlining the process of pagination.

Pagination is an area that needs improvement, but having a count is a must-have feature. Team, please plan this enhancement. The product team should consider this as it’s essential for other business requirements.

Hi Team,

Is there any update on this? As per the business logic, this is a crucial requirement. You may also refer to other platforms for validation.

Looking forward to your response.

Thanks!

Hi ​@Devphoenix,

I see how having this feature would be super useful, and would cut down on extra steps/time to find this info. I’ll reach out to our product team and recommend that they implement this feature, so it’s more likely this gets developed in the future. 

I unfortunately won’t be able to provide a timeline or guarantee regarding this feature’s release, but I’ll definitely stress it’s importance to our team that designs the product.

-Byrne

Hi @chole.strange.

Please let me know asap

Thank you.