Pretty much as the title says, from my application I can’t read channel bans even if the access token has the moderation:read scope granted. Whenever I try to do a request to this endpoint https://api.twitch.tv/helix/moderation/banned?broadcaster_id=<channel_id>&user_id=<user_id> where channel_id i…

[image] Francesco_Jimi: the application/vnd.twitchtv.v5+json Accept header You don’t need this header with Helix [image] Francesco_Jimi: the access token of the broadcaster with the moderation:read scope granted with OAuth You should use the validatity endpoint [image] Authe…

From the validate endpoint I get this response { "client_id": "my-application-client-id", "login": "channel-name", "scopes": [ "moderation:read", "user_read", "user_subscriptions" ], "user_id": "channel-user-id", "expires_in": 9710 } Of course I’ve c…

Very odd, looks like you have a correct token (user token not app access), but the API rejects it. You sure your code doing the call to the ban’s API is using the right token in case you have multiple in play? Aside from that it’s a really odd issue. Try running the call manually cURL on the comma…

I’m actually trying the calls from postman. However I tried using curl and I get the same 401 error [image]

Helix uses "Bearer " not "OAuth " in the header. There is your issue Authorization: Bearer YOURKEY

But…but… [image] Requiring OAuth for Helix Twitch API Endpoints Announcements In an effort to standardize authentication and provide security improvements for the Twitch community, OAuth will soon be required for all Twitch API endpoints in the new Twitch API, also known a…

OAuth is OAuth The prefix is irrelevant. It’s still an OAuth key, but helix requires the prefix to be “bearer” You’ve misunderstood the announcement. [image] Requiring OAuth for Helix Twitch API Endpoints Here is a sample request to show the headers mentioned above. curl -H 'Authorization: B…

Yep, look like I totally did :sweat_smile: Still strange because it used the OAuth prefix until today and has no issues :man_shrugging:

Then that shouldn’t of worked at all. Helix has already required Bearer, and if Twitch snuck in a bug, they have now fixed that bug

Can't read channel bans with moderation:read permission

API

Francesco_Jimi April 16, 2020, 1:08pm 7

But…but…

Topic		Replies	Views
Cannot get banned users - Forbidden 403 API	6	1027	May 24, 2020
Unauthorized - 401 - Insufficient authorization in token API	6	965	April 26, 2021
OAuth Scope issue getting moderator list API	1	783	August 1, 2020
Get Moderators 401 Error API	7	635	June 7, 2021
The ID in moderator_id must match the user ID found in the request's OAuth token API	2	432	March 27, 2023

Can't read channel bans with moderation:read permission

Related topics