Skip to main content

Getting Started

Installation

pip install capo-chime-sdk-messaging

Usage

from capo_chime_sdk_messaging import AsyncChimeSDKMessagingClient


async def main():
    async with AsyncChimeSDKMessagingClient() as chime_sdk_messaging:
        # Example: call the associate_channel_flow operation
        response = await chime_sdk_messaging.associate_channel_flow()
        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_sdk_messaging import AsyncChimeSDKMessagingClient


async def main():
    async with AsyncChimeSDKMessagingClient() as chime_sdk_messaging:
        # Example: paginate over list_channel_bans
        async for item in chime_sdk_messaging.iter_list_channel_bans():
            print(item)

Error Handling

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

from capo_chime_sdk_messaging import AsyncChimeSDKMessagingClient
from capo_chime_sdk_messaging.error import BadRequestException


async def main():
    async with AsyncChimeSDKMessagingClient() as chime_sdk_messaging:
        try:
            await chime_sdk_messaging.associate_channel_flow()
        except BadRequestException 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_sdk_messaging import AsyncChimeSDKMessagingClient


async def main():
    async with AsyncChimeSDKMessagingClient() as chime_sdk_messaging:
        # Default: 3 attempts for every operation
        response = await chime_sdk_messaging.associate_channel_flow()

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

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

Metadata

Release files for capo-chime-sdk-messaging 0.8.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-sdk-messaging 0.8.0
File Size Uploaded Provenance
capo_chime_sdk_messaging-0.8.0.tar.gz 136.2 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-chime-sdk-messaging 0.8.0
File Interpreter ABI Platform
capo_chime_sdk_messaging-0.8.0-py3-none-any.whl Python 3 none any Details

Total release size: 481.2 kB

Release files / capo_chime_sdk_messaging-0.8.0.tar.gz

Download URL capo_chime_sdk_messaging-0.8.0.tar.gz
Size 136.2 kB
Tags Source
SHA-256 checksum
How to use checksums
7ab581be3a47a013696106607d0a128e02dcd09f976a7b41919bda4e82a96e5b
BLAKE2b-256 checksum
How to use checksums
e75b4cb31e2db91b35db13762fc1dfc3607b5dcb5b8bc3fb0c179622cf8a062e
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_sdk_messaging-0.8.0-py3-none-any.whl

Download URL capo_chime_sdk_messaging-0.8.0-py3-none-any.whl
Size 345.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
c0eb7a8441e3dcd695f1632f6b3a4bdb0d408db989000b7501a20a3845d32ecb
BLAKE2b-256 checksum
How to use checksums
37094b4e9a824411021a4408bd6c2163033c170ae69bf3e32a96256986840461
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-sdk-messaging 0.8.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