Getting 403 error on getting current campaigns

Our users are getting 403 errors when trying to retrieve campaigns on the V1 api.
This works for some users, but not for most and we can’t figure out why. They do have campaigns and pledges so that shouldn’t be an issue.

code: 1
code_name: “generic-error”
detail: “A runtime check failed.”
id: “861cc3f7-d398-5705-89ae-7a8ffcaf78c5”
status: “403”
title: “A runtime check failed.”

You can try v2 tokens, calls and endpoints and see if that works out. (should)