1

I use a translator.

Good afternoon. I can’t figure out what I’m doing wrong.

I want to create a subscription to an event (https://api.twitch.tv/helix/eventsub/subscriptions).

Specifically, using channel.chat.message as an example.

I have registered my application. I got the secret key.

Then I generated an address with “all” access areas and sent it to the broadcaster.

I got permission and saved the access key.

Then when I try to create a subscription by specifying in the “Authorization” field the received access key and in the “Client-ID” field the identifier of my application, I get the following response

“auth must use app access token to create webhook subscription”

I saw one thread in the forum about this problem, but I still don’t understand what’s wrong.

Can someone please give me in order, point by point, links to the right methods that need to be executed in a certain order?

2

For webhooks/conduits you must use an app access token also called a client credentials token

Here you have tried to use the users access token.

For webhooks/conduits you do:

  • Generate/obtain a user access token with the relevant permissions for the user ID’s in the condition(s) for the topic you want

  • Store or discard the resultant access token, you only need ti for API (no EventSub Webhook calls)

  • Generate an app access/client credentails token

  • Create Subscriptions

The frist step of generating a user access token creates a permission link between your ClientID and the Users

Blog Post I wrote: How does Twitch’s new EventSub work? – Barry Carlyon
Notes I wrote about chat.message auth: twitch_misc/eventsub/websockets/web/chat at main · BarryCarlyon/twitch_misc · GitHub

So for chat topics as a Webhook

  • Get a user token from the user you want to read chat as (with scopes)
  • Get a user token from the user you want to read the chat of (with scopes)
  • Ignore both tokens
  • Generate a Client Credentials/App Access token (with no scopes)
  • Create Subscriptions
3

you mean this?

4

Yes. That is the link to the documentation for app access aka client credential tokens

1 Like
5

Thank you so much!!! I haven’t seen my mistake all day. But it’s probably a translation problem

6

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.