Skip to main content

capo-connect: typed, async Python SDK for AWS Connect

capo-connect is a typed Python SDK for AWS Connect. It has an async client, AsyncConnectClient, for asyncio and trio, and a sync client, ConnectClient, 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/connect/

Installation

pip install capo-connect

Usage

from capo_connect import AsyncConnectClient


async def main():
    async with AsyncConnectClient() as connect:
        # Example: call the activate_evaluation_form operation
        response = await connect.activate_evaluation_form()
        print(response["evaluation_form_id"])

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_connect import AsyncConnectClient


async def main():
    async with AsyncConnectClient() as connect:
        # Example: paginate over evaluate_data_table_values
        async for item in connect.iter_evaluate_data_table_values():
            print(item)

Error Handling

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

from capo_connect import AsyncConnectClient
from capo_connect.error import InternalServiceException


async def main():
    async with AsyncConnectClient() as connect:
        try:
            await connect.activate_evaluation_form()
        except InternalServiceException 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_connect import AsyncConnectClient


async def main():
    async with AsyncConnectClient() as connect:
        # Default: 3 attempts for every operation
        response = await connect.activate_evaluation_form()

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

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

Metadata

Release files for capo-connect 0.11.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-connect 0.11.0
File Size Uploaded Provenance
capo_connect-0.11.0.tar.gz 976.5 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-connect 0.11.0
File Interpreter ABI Platform
capo_connect-0.11.0-py3-none-any.whl Python 3 none any Details

Total release size: 3.8 MB

Release files / capo_connect-0.11.0.tar.gz

Download URL capo_connect-0.11.0.tar.gz
Size 976.5 kB
Tags Source
SHA-256 checksum
How to use checksums
d711b32f28198ce1e4351a9f651b13ee4c4375a22abf8885466c456c474224ea
BLAKE2b-256 checksum
How to use checksums
1968f3661f988afd8952f1aa036e121082f6d5f3e339b69abb3404d41fbae051
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_connect-0.11.0-py3-none-any.whl

Download URL capo_connect-0.11.0-py3-none-any.whl
Size 2.8 MB
Tags Python 3
SHA-256 checksum
How to use checksums
443f2e4abb3b52f0a81984183d1e263296cb590bd885e890fb3f5b5fd84f0f0e
BLAKE2b-256 checksum
How to use checksums
8d1d967fa4ecc8c09577025fdd1164efaa7f5a10d991b07d4c2bcad515db44b8
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-connect 0.11.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