Skip to main content

capo-kinesis-video-signaling: typed, async Python SDK for AWS Kinesis Video Signaling

capo-kinesis-video-signaling is a typed Python SDK for AWS Kinesis Video Signaling. It has an async client, AsyncKinesisVideoSignalingClient, for asyncio and trio, and a sync client, KinesisVideoSignalingClient, with the same methods. Requests and responses are typed with TypedDicts, so your editor and type checker know every field.

It is part of capo, a community-driven alternative to boto3 and aioboto3, built on its own HTTP stack instead of botocore and generated from the official AWS Smithy models. Documentation: https://capo-sdk.dev/services/kinesis-video-signaling/

Installation

pip install capo-kinesis-video-signaling

Usage

from capo_kinesis_video_signaling import AsyncKinesisVideoSignalingClient


async def main():
    async with AsyncKinesisVideoSignalingClient() as kinesis_video_signaling:
        # Example: call the get_ice_server_config operation
        response = await kinesis_video_signaling.get_ice_server_config()
        print(response["ice_server_list"])

Error Handling

The SDK raises exceptions for errors returned by the API. Catch them to handle failures gracefully.

from capo_kinesis_video_signaling import AsyncKinesisVideoSignalingClient
from capo_kinesis_video_signaling.error import ClientLimitExceededException


async def main():
    async with AsyncKinesisVideoSignalingClient() as kinesis_video_signaling:
        try:
            await kinesis_video_signaling.get_ice_server_config()
        except ClientLimitExceededException as e:
            print(f"Error: {e}")
            print(e.data)  # additional error data

Retrying

The SDK retries failed operations automatically. Retry behaviour follows the Smithy specification: errors are retried based on their is_retryable and is_throttling_error attributes. Throttling errors use a longer base delay. Network-level failures (connection errors and timeouts) are also retried. Non-retryable errors, such as client errors without the @retryable trait, are raised immediately without further attempts.

The number of attempts defaults to 3 and can be changed at the client level via retry_max_attempts, or per call via config_overrides.

from capo_kinesis_video_signaling import AsyncKinesisVideoSignalingClient


async def main():
    async with AsyncKinesisVideoSignalingClient() as kinesis_video_signaling:
        # Default: 3 attempts for every operation
        response = await kinesis_video_signaling.get_ice_server_config()

        # Override per operation
        response = await kinesis_video_signaling.get_ice_server_config(config_overrides={"retry_max_attempts": 5})

        # Disable retries for this call
        response = await kinesis_video_signaling.get_ice_server_config(config_overrides={"retry_max_attempts": 1})

Metadata

Release files for capo-kinesis-video-signaling 0.9.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for capo-kinesis-video-signaling 0.9.0
File Size Uploaded Provenance
capo_kinesis_video_signaling-0.9.0.tar.gz 60.4 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-kinesis-video-signaling 0.9.0
File Interpreter ABI Platform
capo_kinesis_video_signaling-0.9.0-py3-none-any.whl Python 3 none any Details

Total release size: 136.3 kB

Release files / capo_kinesis_video_signaling-0.9.0.tar.gz

Download URL capo_kinesis_video_signaling-0.9.0.tar.gz
Size 60.4 kB
Tags Source
SHA-256 checksum
How to use checksums
c1cf99cfe0538aa96ac8495d2eb242f50292aacb8389a2732be89a0fa5ed9e7e
BLAKE2b-256 checksum
How to use checksums
2dcb3afe8515d063cb93ef4005ad661987839c494f679f04c61bbef67c3ec4a0
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / capo_kinesis_video_signaling-0.9.0-py3-none-any.whl

Download URL capo_kinesis_video_signaling-0.9.0-py3-none-any.whl
Size 76.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
ccfc590d7f552e028eb8a50893ff5fd3bfc13cafb480ef49449f1d1337baaa3d
BLAKE2b-256 checksum
How to use checksums
590124dd70bd36c8deeec73350318023e553c967e515b3cd63be7a89116131f7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Security for capo-kinesis-video-signaling 0.9.0

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.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page