Skip to main content

Getting Started

Installation

pip install capo-chime-sdk-identity

Usage

from capo_chime_sdk_identity import AsyncChimeSDKIdentityClient


async def main():
    async with AsyncChimeSDKIdentityClient() as chime_sdk_identity:
        # Example: call the create_app_instance operation
        response = await chime_sdk_identity.create_app_instance()
        print(response["app_instance_arn"])

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_identity import AsyncChimeSDKIdentityClient


async def main():
    async with AsyncChimeSDKIdentityClient() as chime_sdk_identity:
        # Example: paginate over list_app_instance_admins
        async for item in chime_sdk_identity.iter_list_app_instance_admins():
            print(item)

Error Handling

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

from capo_chime_sdk_identity import AsyncChimeSDKIdentityClient
from capo_chime_sdk_identity.error import BadRequestException


async def main():
    async with AsyncChimeSDKIdentityClient() as chime_sdk_identity:
        try:
            await chime_sdk_identity.create_app_instance()
        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_identity import AsyncChimeSDKIdentityClient


async def main():
    async with AsyncChimeSDKIdentityClient() as chime_sdk_identity:
        # Default: 3 attempts for every operation
        response = await chime_sdk_identity.create_app_instance()

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

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

Metadata

Release files for capo-chime-sdk-identity 0.6.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-identity 0.6.0
File Size Uploaded Provenance
capo_chime_sdk_identity-0.6.0.tar.gz 89.9 kB Without provenance Details

Built distribution (wheel)

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

Total release size: 295.4 kB

Release files / capo_chime_sdk_identity-0.6.0.tar.gz

Download URL capo_chime_sdk_identity-0.6.0.tar.gz
Size 89.9 kB
Tags Source
SHA-256 checksum
How to use checksums
089e4189c1726ca6d7bd2500e99d4a4d8bccd6b7319aea790e9491c40263eb12
BLAKE2b-256 checksum
How to use checksums
4da0b10fbf015b8c7d1be48c384e2ea9b6fd75cc8a94b4ee99252086e469ab4f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.0 {"installer":{"name":"uv","version":"0.13.0","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_identity-0.6.0-py3-none-any.whl

Download URL capo_chime_sdk_identity-0.6.0-py3-none-any.whl
Size 205.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
d1bf703d822cbcc273876bb1fb20b0ec5e95cca9164f69c577ecc0add4d7abd4
BLAKE2b-256 checksum
How to use checksums
2943d52ffa2f5b3bc0204cebda9ec1454370bb295abf749e9669b89ec5b21d24
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.0 {"installer":{"name":"uv","version":"0.13.0","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-identity 0.6.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