Skip to main content

capo-chime: typed, async Python SDK for AWS Chime

capo-chime is a typed Python SDK for AWS Chime. It has an async client, AsyncChimeClient, for asyncio and trio, and a sync client, ChimeClient, 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/chime/

Installation

pip install capo-chime

Usage

from capo_chime import AsyncChimeClient


async def main():
    async with AsyncChimeClient() as chime:
        # Example: call the associate_phone_number_with_user operation
        response = await chime.associate_phone_number_with_user()
        print(response)

Pagination

Some operations in this SDK support pagination. If the operation supports pagination it will have an iter_ prefixed method that returns an async iterator.

from capo_chime import AsyncChimeClient


async def main():
    async with AsyncChimeClient() as chime:
        # Example: paginate over list_accounts
        async for item in chime.iter_list_accounts():
            print(item)

Error Handling

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

from capo_chime import AsyncChimeClient
from capo_chime.error import AccessDeniedException


async def main():
    async with AsyncChimeClient() as chime:
        try:
            await chime.associate_phone_number_with_user()
        except AccessDeniedException 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_chime import AsyncChimeClient


async def main():
    async with AsyncChimeClient() as chime:
        # Default: 3 attempts for every operation
        response = await chime.associate_phone_number_with_user()

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

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

Metadata

Release files for capo-chime 0.10.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-chime 0.10.0
File Size Uploaded Provenance
capo_chime-0.10.0.tar.gz 137.1 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-chime 0.10.0
File Interpreter ABI Platform
capo_chime-0.10.0-py3-none-any.whl Python 3 none any Details

Total release size: 484.3 kB

Release files / capo_chime-0.10.0.tar.gz

Download URL capo_chime-0.10.0.tar.gz
Size 137.1 kB
Tags Source
SHA-256 checksum
How to use checksums
dae994824cecd3f1b8d135b8ecec92ad73dae8e6073d247021d04bde4c02469f
BLAKE2b-256 checksum
How to use checksums
3b6430877a5a4dcfcfa2ccfdcb3c19e9def05832e8fbf281286ac9f08f792279
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_chime-0.10.0-py3-none-any.whl

Download URL capo_chime-0.10.0-py3-none-any.whl
Size 347.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
885cafbe8c4c6d5d6a0601143e126f27386bb109ce2c4c1bd2749475b5b9ae6e
BLAKE2b-256 checksum
How to use checksums
97d271d8da9632b8ad0a3ecd7f6dd10d707eb4e2a1e111012b4fd56b4384ed53
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-chime 0.10.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