Cannot call addUpvote/removeUpvote mutations using app-issued user token #3968
Replies: 5 comments 2 replies
-
Thanks for reporting this! You're right, those mutations don't currently support integrations. I've added this to our engineering todo list. I can't promise a timeframe for when we'll have a fix for this deployed, but we'll be sure to post an update here once it is! |
Beta Was this translation helpful? Give feedback.
-
Hey any luck on this issue? :) |
Beta Was this translation helpful? Give feedback.
-
👋 I've reopened the original issue in our backlog, hopefully we'll get more traction this time around 😅 |
Beta Was this translation helpful? Give feedback.
-
@antn @Bestra It'd be really useful to get this sorted; is it a complicated engineering adjustment, or is there some way the community can help? It would be helpful to understand how the Discussions API and the features within it are being prioritized. |
Beta Was this translation helpful? Give feedback.
-
Hi,
For the past two months, I've been working on giscus, a comments widget built on GitHub Discussions. It utilizes the Discussions API to let users sign in with GitHub and leave comments on your website, linking the page with a matching discussion.
Apart from the limitations of the Discussions API (e.g. #3622 and isaacs/github#972), it's been working great. However, when I implemented the upvote toggle feature, I keep getting a
FORBIDDEN: Resource not accessible by integration
error when I call theaddUpvote
/removeUpvote
GraphQL operations using an app-issued user token (ghu_xxx...
). Using a personal access token works fine.The app already has read and write permissions to Discussions. You can try leaving a comment on the website or adding/removing reactions to comments and see that they work.
I've even tried enabling all permissions on the app, but I still got the same error.
Will this be fixed? Thanks!
Beta Was this translation helpful? Give feedback.
All reactions