We're seeing the /pakms/apikey endpoint failing with {"message":"401 Unauthorized"} in production after the recent migration. Sandbox is working and the auth tokens we tested in production are working fine for other api calls.
We're seeing the /pakms/apikey endpoint failing with {"message":"401 Unauthorized"} in production after the recent migration. Sandbox is working and the auth tokens we tested in production are working fine for other api calls.
This issue has been resolved.
Hi David. We have been following this thread as we have dozens of apps down due to this issue. As of 2 minutes ago, we are still experiencing this issue.
Provide your app id please. I just checked the logs again and the 401s have dropped off a cliff, I don't see any since 10:45. I am guessing you are getting a lag in your reports.
Also, please note the the pakms/apikey endpoint is not meant to be called per payment. You should be obtaining the token 1 time per merchant, storing it, and pulling it from the store for subsequent payments.
2 People are following this question.