Replies posted by jjdinho

3 Replies

Newest first

Oldest first

jjdinhoContributor II

asked in Developer Group

V2 API key invalid for Get List and Segment Members but is valid for other requests

Hey Brian,Thanks for your response. I agree with your analysis and think that it probably was key permissions-related.I would recommended updating the error sent back in the response for this kind of situation. According to the documentation, a key permission issue should probably return a 401 error ("Not Authorized: Key is valid, but account does not have permissions to perform this action"). For me, it was returning a 403 error ("Forbidden: Request is missing or has an invalid API key"), which is misleading, because the key was working for many other requests/endpoints.Thanks again for getting back to me.Jake

1 year ago

jjdinhoContributor II

asked in Developer Group

V2 API key invalid for Get List and Segment Members but is valid for other requests

Any update on this @Brian Turcotte ?

1 year ago

jjdinhoContributor II

asked in Developer Group

V2 API key invalid for Get List and Segment Members but is valid for other requests

Hey Brian,Thanks for you timely response.I dug a bit deeper and found some details that could help: I am using a Segment ID. This segment id is the first value return when querying the "v1/lists" endpoint. So the segment definitely exists. But I still get a 403 error code response when using that Segment ID to query the "v2/group/LIST_OR_SEGMENT_ID/members/all" endpoint.Could it be that the api key has permission to read list data but not segment data? Or that is does not have permission to read member data of lists & segments?It that was the case, however, I would expect a 401 error response, according to the documentation.Hope that info helps.Thanks again.Jake

1 year ago

New Topic Guidelines

If you’ve already contacted the Klaviyo Support Team about this issue, please wait for a response and check your spam inbox for an email before posting in the Community.

Keep your private information private. That means, leave out information such as email address, links to account, private API key, customer info, etc. out of your posts.

Collaborate and discuss ideas in a positive and respectful manner. We are all here to learn and work together.

Promotion of other products/services should be relevant to the original post. The product/service should directly assist the community member with their issue.

Include as much detail as you can in your posts where applicable. The more information (integration, error message, screenshot, etc.) you include, the easier other Community members can assist or add to your discussion.

Starting a discussion or writing a feature request? Let people know how they can join in or provide feedback! Are you looking for others to share their thoughts, recommendations, examples, etc? Be as specific as you can where applicable.

Most helpful members this week

Terms & Conditions Cookie settings

Sign up

Already have an account? Login

Use your Klaviyo credentials

Log in to the Community

Use your Klaviyo credentials

Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.

Username or e-mail

Back to overview

Scanning file for viruses.

Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.

This file cannot be downloaded

Sorry, our virus scanner detected that this file isn't safe to download.

Links & Resources

Klaviyo.com
Log in to Klaviyo
Klaviyo Blog
Help Center
Marketing resources
Live training

Platforms

Klaviyo for Shopify
Klaviyo for Shopify Plus
Klaviyo for BigCommerce
Klaviyo for Commerce Cloud
Klaviyo for Magento
Klaviyo for WooCommerce
Direct Integrations

Partners

Klaviyo Partner Programs
Agency Partner Directory
Integrations Library

Useful Things

COVID-19 Insights
Events
Email Template Builder
API Docs
Get Help

About

Who We Are
Newsroom
Careers
Engineering Blog
Design Blog
Contact Us