No, I wouldn't think the docs themselves would, but I figured maybe there was an actual API update that might have rolled out at the same time.
Hi @MahlerFive
Can you provide the specific call that's giving you the 401?
This fails with 401 when I attempt them myself:
https://apisandbox.dev.clover.com/v3/merchants/4NA1S2T4K3ERR/customers?access_token=[token]&limit=5&offset=0
Other calls fail as well from my app which were automated, such as the customers.csv endpoint.
Our records indicate that you've changed your permissions as recently as today. Are you still seeing the 401 error?
Taking another look at your query, the merchant ID that you're using is actually your app ID. You'll want to make sure you're using the merchant's ID instead.
I already tried reinstalling the app on the test merchant which I wrote in the original post. Still didn't work after getting a new token.
Just tried reinstalling again and same problem - can get a new api token, can see it has the proper permissions, but get back 401s on my get requests.
1 Person is following this question.