Skip to main content
Contributor III
April 6, 2022
Solved

403 errors on Get Profile endpoint

  • April 6, 2022
  • 13 replies
  • 1300 views

We have an integration between our platform (MentionMe) and Klaviyo and we’ve recently been seeing more and more 403 errors when calling the Get Profile endpoint (https://developers.klaviyo.com/en/reference/get-profile). Think we saw this first ones on 15 March, and last night we saw about 150 of these for various Klaviyo clients.

I had a look at our logs and the response we’re getting from the API is the one bellow:

[image removed]

These seems to usually happen during the night. For example, last night we had errors between 06/04/2022 02:14:02 - 06/04/2022 04:08:31

I’ve checked the Klaviyo status page but there is no incident reported there.

 

Has anyone else seen something similar?

This topic has been closed for replies.
Best answer by IainD

Hi @alex.hong 

All fixed now - no errors over the last 2 days having had multiple errors per day over the previous 2 weeks. Please thank your developers ;-)

To answer your questions, though, I think AppScript uses multiple IPs - see https://stackoverflow.com/questions/66919433/how-to-know-ip-of-urlfetchapp-in-google-apps-script

It would be easy to add retry requests but the data is not mission critical so I can afford a few fails per day.

Many thanks

Iain

13 replies

Contributor I
September 27, 2022

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?

alex.hong
Klaviyo Alum
September 27, 2022

Hi @lsamuels ,

I would try that first and if the problems seem to persist, then contact our Support team to see if there are any errors and the disconnects aren’t just random.

Active Contributor II
January 18, 2023

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