Comments (2)
The CLI is just a test tool to send an example payload to your EventSub Callback.
So you don't have to use the dashboard/live Twitch to Trigger a "Channel update"
Essentailly the migration from WebSub to EventSub is straightforward:
- Challenges are over POST now instead of GET
- The Signature is calculated slightly differently.
- The payloads are a different format
Depending on your language of choice, I have a node and a PHP example over at https://github.com/BarryCarlyon/twitch_misc/tree/main/eventsub/handlers
And you can use the CLI to punt test messages at your callback based on my code.
So the CLI just does the same thing as the live website does. It's just easier to spam a CLI command than to ask the live system to do send a payload. (and lets you test parsing subscriber data without needing an affiliate or partner or to spend money to trigger an event)
from twitch-cli.
ooh, that would certainly explain my struggle to find the documentation for it. Updated my old code from WebSub to EventSub and seems to be working now. Will have to give this cli a try to send some dummy events through.
Thank you for the clear and thorough reply.
from twitch-cli.
Related Issues (20)
- EventSub WebSocket REST endpoints showing subscriptions when not necessary
- Validate token feature HOT 3
- Mock API /charity/donations should use target_amount instead of amount
- [Feature Request] add TwitchCLI to winget HOT 2
- Unused variable err
- [Bug] Using verify-subscription channel.follow requires version param HOT 1
- [Bug] Twitch token subcommand fails with segmentation fault
- Simulate Keepalive Message Interruption [Feature Request] HOT 1
- [Bug] Endpoint returns different response than twitch docs
- [Feature Request] Implement usage of Refresh Token HOT 1
- Clarify error message when failing to forward WebSocket events
- [Bug] channel.follow puts Broadcaster ID in Broadcaster User Login
- [Feature Request] Support DCF on token generation
- [Bug] twitch token provides no token when using Public client type
- Forwarding events carried over after WebSocket reconnect doesn't work HOT 1
- EventSub Subscriptions are a child of a single WebSocket server
- [Bug] Websocket reconnect old socket doesn't emit HOT 2
- [Bug] Cannot set Custom Reward `is_paused` field to `false`
- [Bug] Verification fails for "event trigger" (but passed for "event verify-subscription") - regression in 1.1.23 against the 1.1.22 HOT 3
- [Bug] mock event websocket server ignores a valid 'session'
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from twitch-cli.