Kick, without the I/O.

kicksdk knows Kick: which requests to make and what the answers look like, how the realtime chat feed speaks, how webhooks are signed. Your code sends the requests and holds the sockets; kicksdk does the rest, from one Rust core, in five languages.

Install

cargo add kicksdk

npm install kicksdk-js

pip install "kicksdk-py[aio]"

dart pub add kicksdk

{:kicksdk, "~> 0.2"}

Two things to know first

The chat feed only accepts kick.com. Kick's realtime server refuses a WebSocket whose Origin is not https://kick.com. Servers set it (every connectChat does); a browser cannot, so in a browser the feed works only on kick.com, in a page or an extension's content script. Anywhere else, relay it through a server.

Much of Kick is unofficial. The website API and the realtime feed are what kick.com's own frontend uses, not a published API, and can change without notice. The official API and webhooks are the stable part. Everything known about each, with where it was seen, is in the Kick reference.

Every function, in every language

Each core function and its name in each package, read from the sources when this site was built. Requests come back as {method, url, headers, body} for your HTTP client; parsers take the status and body. The realtime Session (open, receive, tick, refresh, closed) and connectChat are in each language's reference.