Skip to main content

Getting Started

Installation

pip install capo-connecthealth

Usage

from capo_connecthealth import AsyncConnectHealthClient


async def main():
    async with AsyncConnectHealthClient() as connect_health:
        # Example: call the activate_subscription operation
        response = await connect_health.activate_subscription()
        print(response["subscription"])

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_connecthealth import AsyncConnectHealthClient


async def main():
    async with AsyncConnectHealthClient() as connect_health:
        # Example: paginate over list_domains
        async for item in connect_health.iter_list_domains():
            print(item)

Streaming Request

Some operations accept a streaming request body. Pass an async iterator of bytes chunks, or the whole body as bytes, for the streaming parameter.

A plain iterator can be sent only once, so if a request fails after its body was transmitted the operation is not retried. To get retries for streamed uploads, pass a Body instead: it wraps a source that can be reopened, and every attempt streams a fresh copy. Body.from_path (sync client) and Body.async_from_path (async client, needs anyio) stream a file from disk; Body(opener) takes any context manager that yields a (stream, length) pair.

from capo_connecthealth import AsyncConnectHealthClient, Body


async def main():
    async with AsyncConnectHealthClient() as connect_health:
        # Example: call start_medical_scribe_listening_session with a streaming request body
        async def chunks():
            yield b'Hello, World!'

        response = await connect_health.start_medical_scribe_listening_session(input_stream=chunks())
        print(response)

        # Or pass the whole body as bytes
        response = await connect_health.start_medical_scribe_listening_session(input_stream=b'Hello, World!')
        print(response)

        # Or stream a file with Body: the file is reopened on every retry
        # and Content-Length is taken from its size, so no content_length needed
        response = await connect_health.start_medical_scribe_listening_session(input_stream=Body.async_from_path("hello.txt"))
        print(response)

Error Handling

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

from capo_connecthealth import AsyncConnectHealthClient
from capo_connecthealth.error import AccessDeniedException


async def main():
    async with AsyncConnectHealthClient() as connect_health:
        try:
            await connect_health.activate_subscription()
        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_connecthealth import AsyncConnectHealthClient


async def main():
    async with AsyncConnectHealthClient() as connect_health:
        # Default: 3 attempts for every operation
        response = await connect_health.activate_subscription()

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

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

Metadata

Release files for capo-connecthealth 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-connecthealth 0.6.0
File Size Uploaded Provenance
capo_connecthealth-0.6.0.tar.gz 92.2 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-connecthealth 0.6.0
File Interpreter ABI Platform
capo_connecthealth-0.6.0-py3-none-any.whl Python 3 none any Details

Total release size: 265.9 kB

Release files / capo_connecthealth-0.6.0.tar.gz

Download URL capo_connecthealth-0.6.0.tar.gz
Size 92.2 kB
Tags Source
SHA-256 checksum
How to use checksums
6035fb91cd68f6f20e9b29ab431ab2a400c8e8d1d46ec250f73ce193e9d8a221
BLAKE2b-256 checksum
How to use checksums
5b7ae8485a27db562c92b2cdd69ef5b2db8383767d84561db19db9e7c09840a7
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_connecthealth-0.6.0-py3-none-any.whl

Download URL capo_connecthealth-0.6.0-py3-none-any.whl
Size 173.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
544684beb73fbcbaf00a7c4e252748006f3144307a60702c7d0f536ec853d744
BLAKE2b-256 checksum
How to use checksums
dee40dba0ffb73aed4ef05db56e902599ea9c8e2c8fa890edb97469e91393ef0
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-connecthealth 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