I’m getting You are not permitted to view the requested resource. The API username or key is invalid. responses from your server when trying to push an update to a topic. I started out using a key that I’ve been using now for a while (years?). Thinking perhaps there was a policy update I went to create a new key. The original (previously working) key was associated with the main admin account. That account is no longer available in the user-dropdown. So I created a new key for my personal user account (also admin, but not the main site admin) and I’m getting the same error. Is there a policy configuration I need to make to use this new key?

Since you are hosted with us, I did a quick check in your site and the key looks good. Could you please share the request you are sending? What parameters are you setting? Is it possible you are using the wrong username? If you have any privacy concern, we can turn this into a PM.

Issues using API with long-established/working key

Product Support

guildai (Garrett) April 20, 2022, 6:53pm 3

Ack yes it was the username! I assumed the API key itself was associated with a user - wrong! I should have checked that

Thanks for the help!

Topic		Replies	Views
Unable to create new topic via API Development	0	739	March 31, 2020
Invalid Access using Global Key on All users Development rest-api	2	1010	November 29, 2020
Newly enforced api_username restriction? Development rest-api	4	654	October 29, 2020
Generate/Regenerate api_key for a user API not working Development rest-api	4	1032	December 6, 2019
Triggering a backup via admin API causes the api_key to become only valid for system user Bug	7	1281	September 4, 2018

Issues using API with long-established/working key

Related topics