403 errors on Get Profile endpoint

Tips to fix-

Check the . htaccess File. 
Reset File and Directory Permissions. 
Disable WordPress Plugins. 
Upload an Index Page. 
Edit File Ownership. 
Verify the A Record. 
Scan for Malware. 
Clear Your Web History/Cache.

Regards,

Rachel Gomez

Hi community! I’m on magento2 with direct api connection. fastly/cloudflare. The 403 errors are still coming up for us seemingly randomly/intermittently and blocking email traffic. Should I create new api keys to clear up the issue?

Hey @alexoanea,

I would suggest trying again to see if those requests were still getting block. 

We recently noticed an incident regarding a partial API outage causing an elevation in 403 errors. You can find more details and subscribe to the public incident report here. 

David

Hi Alex and Alex

I’m experiencing the same problem...

I’m calling the metrics API (https://a.klaviyo.com/api/v1/metrics) from Google Sheets using AppScript for reporting purposes.

Looking at my error logs, I can see that the problem started suddenly on 29th March. Seven error 403s were reported on that day compared to none in the previous month… Now I get error notifications every day with up to 50% of daily calls failing in some cases (I’m calling the API every 6 hours).

Look forward to your thoughts Alex H…

Thanks, Iain

Hi there @alexoanea,

To start, I will say that although we use Cloudflare, I cannot request for one-off IPs to be whitelisted as there is a much more detailed process behind that.

I'm slightly confused what it is that you are trying to do. It sounds like you are using a third party tool to integrate a different software with Klaviyo but when making that v1/person request its being denied/blocked with a 403 aka a server/authentication issue. I think there is something more systematic than Klaviyo's cloudflare blocking these accounts. If you could further explain your goals and how you want the data to interact between Klaviyo, MentionMe, and tray.io that could help.

Additional note, the time of day should not be a variable.

All the best,

Alex

Hi there@alexoanea,

Welcome to the Community,

A relatively common reason for this is if you have a firewall or other security measures in place that may be rate-limiting or blocking Klaviyo after detecting large transfers of data. The solution to this is to whitelist Klaviyo. As Klaviyo uses dynamic IPs, we do not provide a range of IPs to customers. Instead, we recommend whitelisting our user agent, which is: Klaviyo/1.0

This could also be due to a bad API key, syntax error, or due to be running from javascript. See "group memberships" in the API documentation.

If not, it could be that you're using our server side endpoint for a client side call. If this is the case, I would recommend switching this as I don't think we will allow cross origin requests.
Here is an example ajax call that you should be able to utilize if you're sending from the client side:
 

var settings = {
  "async": true,
  "crossDomain": true,
  "url": "https://manage.kmail-lists.com/ajax/subscriptions/subscribe",
  "method": "POST",
  "headers": {
    "content-type": "application/x-www-form-urlencoded",
    "cache-control": "no-cache"
  },
  "data": {
    "g": “{{LIST_ID}}",
    "$fields": "vote",
    "email": “{{email}}",
    "vote": "vote"
  }
}

$.ajax(settings).done(function (response) {
  console.log(response);
});

Additional info can be found here.

Thanks!
Alex