You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’m currently developing a bot that interacts with Kick's API to automatically create clips from live streams based on chat commands. The idea is to allow viewers to trigger the bot with a command (e.g., !clip) and have it capture the most recent 30 seconds of the stream.
I’ve encountered some issues while integrating the WebSocket API for chat functionality. Specifically, I am receiving an ENOTFOUND error when trying to connect to the WebSocket endpoint wss://chat.kick.com. After researching, I noticed that Kick provides separate APIs for chat and user management, and I’m wondering if these might be more suitable for my use case.
Here's what I need help with:
Correct WebSocket endpoint: If anyone has successfully connected to Kick’s WebSocket API for chat, could you share the correct URL or any changes I might need to make in the code to resolve the ENOTFOUND error?
Using Chat and User APIs effectively: Is it possible to use Kick's chat and user APIs together with WebSocket for clip creation, or should I be focusing on other endpoints for stream data?
Best practices for bot development: If you have experience building bots with Kick's API, I’d love any advice on how to handle chat interactions and clip creation efficiently.
I’d appreciate any help or insights on how to proceed. Thank you!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hello everyone,
I’m currently developing a bot that interacts with Kick's API to automatically create clips from live streams based on chat commands. The idea is to allow viewers to trigger the bot with a command (e.g., !clip) and have it capture the most recent 30 seconds of the stream.
I’ve encountered some issues while integrating the WebSocket API for chat functionality. Specifically, I am receiving an ENOTFOUND error when trying to connect to the WebSocket endpoint wss://chat.kick.com. After researching, I noticed that Kick provides separate APIs for chat and user management, and I’m wondering if these might be more suitable for my use case.
Here's what I need help with:
Correct WebSocket endpoint: If anyone has successfully connected to Kick’s WebSocket API for chat, could you share the correct URL or any changes I might need to make in the code to resolve the ENOTFOUND error?
Using Chat and User APIs effectively: Is it possible to use Kick's chat and user APIs together with WebSocket for clip creation, or should I be focusing on other endpoints for stream data?
Best practices for bot development: If you have experience building bots with Kick's API, I’d love any advice on how to handle chat interactions and clip creation efficiently.
I’d appreciate any help or insights on how to proceed. Thank you!
Beta Was this translation helpful? Give feedback.
All reactions