Invision Community 4: SEO, prepare for v5 and dormant account notifications Matt November 11, 2024Nov 11
Posted November 12, 20186 yr If the method is commented to have @apiclientonly in the docblock, instead of denying only OAuth Access Token use, it denies any use other than API key. This is directly counter the documentation: https://invisioncommunity.com/developers/rest-api?endpoint=core/members/POSTindex On the surface, the problem seems to be that such methods are not actually available to be granted permissions in the scopes selection form in the ACP for Oauth Client Credentials. I can't imagine this is intended given the documentation and code. I would appreciate it if this could be looked into, thank you. It is vastly preferred to use the security superior oauth for such work.
November 13, 20186 yr Author { "errorCode": "2S291\/3", "errorMessage": "NO_PERMISSION" } To note, Other calls to endpoints actually listed in the scopes tab for oAuth Client config work: The same for an API Key: Note the missing endpoints in the former's case. I suspect this to be the root cause.
Archived
This topic is now archived and is closed to further replies.