Skip to main content

Getting Started

Installation

pip install capo-workmailmessageflow

Usage

from capo_workmailmessageflow import AsyncWorkMailMessageFlowClient


async def main():
    async with AsyncWorkMailMessageFlowClient() as work_mail_message_flow:
        # Example: call the get_raw_message_content operation
        response = await work_mail_message_flow.get_raw_message_content()
        print(response["message_content"])

Streaming Response

Some operations return a streaming response body. Use the operation as an async context manager and iterate over the response field to read chunks.

from capo_workmailmessageflow import AsyncWorkMailMessageFlowClient


async def main():
    async with AsyncWorkMailMessageFlowClient() as work_mail_message_flow:
        # Example: call get_raw_message_content and read the streaming response
        async with work_mail_message_flow.get_raw_message_content() as response:
            async for chunk in response["message_content"]:
                print(chunk)

Error Handling

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

from capo_workmailmessageflow import AsyncWorkMailMessageFlowClient
from capo_workmailmessageflow.error import ResourceNotFoundException


async def main():
    async with AsyncWorkMailMessageFlowClient() as work_mail_message_flow:
        try:
            await work_mail_message_flow.get_raw_message_content()
        except ResourceNotFoundException 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_workmailmessageflow import AsyncWorkMailMessageFlowClient


async def main():
    async with AsyncWorkMailMessageFlowClient() as work_mail_message_flow:
        # Default: 3 attempts for every operation
        response = await work_mail_message_flow.get_raw_message_content()

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

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

Metadata

Release files for capo-workmailmessageflow 0.5.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-workmailmessageflow 0.5.0
File Size Uploaded Provenance
capo_workmailmessageflow-0.5.0.tar.gz 54.1 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-workmailmessageflow 0.5.0
File Interpreter ABI Platform
capo_workmailmessageflow-0.5.0-py3-none-any.whl Python 3 none any Details

Total release size: 119.4 kB

Release files / capo_workmailmessageflow-0.5.0.tar.gz

Download URL capo_workmailmessageflow-0.5.0.tar.gz
Size 54.1 kB
Tags Source
SHA-256 checksum
How to use checksums
181b2f16886b0e4b487fbd1a981c690ad09369396a91ae90b26b5db7318a394c
BLAKE2b-256 checksum
How to use checksums
f7b2d3004c6be263dae0007c9ccecc527410364c1016404978c6cbdda366878e
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_workmailmessageflow-0.5.0-py3-none-any.whl

Download URL capo_workmailmessageflow-0.5.0-py3-none-any.whl
Size 65.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
588386c206259030ea359688c9155718ddf64d44ff8dcf2754a18c9a44de1baf
BLAKE2b-256 checksum
How to use checksums
13303cdb412e5e3abd4e5911729aa0362345bf218d29723b7d89b949db66318a
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-workmailmessageflow 0.5.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