kicksdk (Python)
Kick (kick.com) without the I/O: requests, response parsers, the realtime chat protocol and webhook verification, from the kicksdk Rust core.
pip install kicksdk-py # the core
pip install "kicksdk-py[aio]" # plus connect_chat over asyncio (httpx, websockets)
The import is kicksdk. (On PyPI the name is kicksdk-py: PyPI treats
kicksdk as too close to the unrelated kick-sdk.)
import asyncio, kicksdk.aio
async def main():
async with kicksdk.aio.connect_chat(chatroom_id, channel_id) as chat:
async for e in chat:
ev = e["event"]
if ev["type"] == "chat_message":
print(ev["sender"]["username"], ev["content"])
asyncio.run(main())
connect_chat reconnects by itself until the async with block ends, which
closes the socket normally. After network errors, 5xx answers and dropped
sockets it waits a jittered backoff (1 s doubling to 30 s); when Kick refuses
the client (a ban, a refused token, a terminal close code), or after
max_refusals (5) refused attempts in a row (a 403, say), it waits 5 minutes
or more (10, 20, then 30 for more in a row) and comes back as a new client.
Only an unexpected error (a bug) ends it early, raised by the async for.
chat.last_drop says why the last connection ended and how long the wait
is, chat.retrying whether it is waiting now, and the kicksdk.aio logger
reports each drop. A failed token refresh keeps
the connection. Events the consumer has not read wait in a buffer of
max_queue (10,000); when it is full, overflow="drop_oldest" (the
default) drops the oldest and counts them in chat.dropped, and
overflow="backpressure" stops reading the socket until there is room. The
kicksdk.aio module docs have the details.
Everything else returns kicksdk.Request objects for any HTTP client and
parses what comes back (kicksdk.website.channel_request /
parse_channel, kicksdk.public_api.livestreams_requests,
kicksdk.webhooks.verify, …). Errors are kicksdk.KickError with kind and
status.
kicksdk.webhooks.verify(public_key_pem, headers, body) takes the body as
received (bytes, or str) and refuses a delivery more than 5 minutes from
now (now= in Unix seconds, tolerance_secs=), so an old one cannot be
replayed; skip_freshness=True re-checks a stored one.
Wheels are built for Linux, macOS and Windows (CPython 3.9+, one abi3 wheel per platform). Anywhere else pip builds from the source distribution, which needs a Rust toolchain.
Kick's realtime server only accepts Origin: https://kick.com; connect_chat
sends it. MIT OR Apache-2.0. Not affiliated with Kick.
Metadata
Release files for kicksdk-py 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| kicksdk_py-0.2.0.tar.gz | 94.4 kB | Details |
Built distributions (wheels)
| File | Reset | |||
|---|---|---|---|---|
| kicksdk_py-0.2.0-cp39-abi3-win_arm64.whl | CPython 3.9 | abi3 | Windows ARM64 | Details |
| kicksdk_py-0.2.0-cp39-abi3-win_amd64.whl | CPython 3.9 | abi3 | Windows x86-64 | Details |
| kicksdk_py-0.2.0-cp39-abi3-musllinux_1_2_x86_64.whl | CPython 3.9 | abi3 | Linux musl 1.2+ x86-64 | Details |
| kicksdk_py-0.2.0-cp39-abi3-musllinux_1_2_aarch64.whl | CPython 3.9 | abi3 | Linux musl 1.2+ ARM64 | Details |
| kicksdk_py-0.2.0-cp39-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl | CPython 3.9 | abi3 | Linux glibc 2.17+ x86-64 | Details |
| kicksdk_py-0.2.0-cp39-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl | CPython 3.9 | abi3 | Linux glibc 2.17+ ARM64 | Details |
| kicksdk_py-0.2.0-cp39-abi3-macosx_11_0_arm64.whl | CPython 3.9 | abi3 | macOS 11.0+ ARM64 | Details |
| kicksdk_py-0.2.0-cp39-abi3-macosx_10_12_x86_64.whl | CPython 3.9 | abi3 | macOS 10.12+ x86-64 | Details |
Total release size: 3.9 MB
Release files / kicksdk_py-0.2.0.tar.gz
| Download URL | kicksdk_py-0.2.0.tar.gz |
|---|---|
| Size | 94.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
37881fa057911bae76871863614107bad0a2a7586b48430449dd28d7284202c8
|
|
BLAKE2b-256 checksum How to use checksums |
05dadde2535eee86734085e4cd12d7b8b33de976a435bfd4ad81093604e36172
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.
Transparency logRelease files / kicksdk_py-0.2.0-cp39-abi3-win_arm64.whl
| Download URL | kicksdk_py-0.2.0-cp39-abi3-win_arm64.whl |
|---|---|
| Size | 367.0 kB |
| Tags | CPython 3.9 Windows ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
65d554cd5703d04149cbb9bc9bd15ae9a743d7cf51597880b5d33518db525f59
|
|
BLAKE2b-256 checksum How to use checksums |
4e18a57398baa24c8109ba0d49aa5896f6d1ce7caafb38811ccfed28014cfca3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.
Transparency logRelease files / kicksdk_py-0.2.0-cp39-abi3-win_amd64.whl
| Download URL | kicksdk_py-0.2.0-cp39-abi3-win_amd64.whl |
|---|---|
| Size | 377.3 kB |
| Tags | CPython 3.9 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
0595c340b12d93980d29103a24d35b1179f4e52f4a802ade59c1a3f76a88ecd7
|
|
BLAKE2b-256 checksum How to use checksums |
0542699dd5d1142d617511248d7b328585c1d9cee958ec46d868b0a63f40bca3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.
Transparency logRelease files / kicksdk_py-0.2.0-cp39-abi3-musllinux_1_2_x86_64.whl
| Download URL | kicksdk_py-0.2.0-cp39-abi3-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 666.6 kB |
| Tags | CPython 3.9 Linux musl 1.2+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
e5bf481f70f1d8ac4a2bc722716096dcdb8b774d8f1a8234000d83b6b13a3cbd
|
|
BLAKE2b-256 checksum How to use checksums |
c557510d534387df68166de019441d3c5633e5a8c21acd7c3b2a8a239fa27eed
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.
Transparency logRelease files / kicksdk_py-0.2.0-cp39-abi3-musllinux_1_2_aarch64.whl
| Download URL | kicksdk_py-0.2.0-cp39-abi3-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 613.0 kB |
| Tags | CPython 3.9 Linux musl 1.2+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
fc39cd43c7777204943d3859fb9c01f6cba96cdb6366b1b221e0740b55b92784
|
|
BLAKE2b-256 checksum How to use checksums |
dac4829897d1138bd70ae2896c498f31401fe40e1317bc4742b179f448d07fd5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.
Transparency logRelease files / kicksdk_py-0.2.0-cp39-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | kicksdk_py-0.2.0-cp39-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 454.1 kB |
| Tags | CPython 3.9 Linux glibc 2.17+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
dc8197a264d095637998813e7de137e9da9ea55829da8666e9a2c64f5c838900
|
|
BLAKE2b-256 checksum How to use checksums |
fd5882d9f2b63f5eb2d425b27f747b63defa8585544dc5a7657557921d9bffd2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.
Transparency logRelease files / kicksdk_py-0.2.0-cp39-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | kicksdk_py-0.2.0-cp39-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 435.1 kB |
| Tags | CPython 3.9 Linux glibc 2.17+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
febc4a86b3f8d459dd9cbb670aa53bf6c0b5e4aa5a9b26219c0c5450a49fe55f
|
|
BLAKE2b-256 checksum How to use checksums |
fe901951fd128aaea177b0947336074eb16d69ee37d4459ce6c7795a89cfb893
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.
Transparency logRelease files / kicksdk_py-0.2.0-cp39-abi3-macosx_11_0_arm64.whl
| Download URL | kicksdk_py-0.2.0-cp39-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 426.6 kB |
| Tags | CPython 3.9 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
2e8b1cebd88fa3d4c05d732ec7e963ef60805f9f3b83d7531203df26ac1eafaf
|
|
BLAKE2b-256 checksum How to use checksums |
2ed4f842062be9d0067cffa05513ec4c120e9ae26d39b8bc5fa1fb1351d5092c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.
Transparency logRelease files / kicksdk_py-0.2.0-cp39-abi3-macosx_10_12_x86_64.whl
| Download URL | kicksdk_py-0.2.0-cp39-abi3-macosx_10_12_x86_64.whl |
|---|---|
| Size | 441.4 kB |
| Tags | CPython 3.9 abi3 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
6fc800824b7516c900acbd38b4696f7f138bf629691339f3abfb5eaed92c842c
|
|
BLAKE2b-256 checksum How to use checksums |
35e7e6a7b4da22cafcabd9f8439d70b5ba96f2a4afec902aeafabf49fb2f611b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.
Transparency log