Skip to main content

Getting Started

Installation

pip install capo-partnercentral-benefits

Usage

from capo_partnercentral_benefits import AsyncPartnerCentralBenefitsClient


async def main():
    async with AsyncPartnerCentralBenefitsClient() as partner_central_benefits:
        # Example: call the amend_benefit_application operation
        response = await partner_central_benefits.amend_benefit_application()
        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_partnercentral_benefits import AsyncPartnerCentralBenefitsClient


async def main():
    async with AsyncPartnerCentralBenefitsClient() as partner_central_benefits:
        # Example: paginate over list_benefit_allocations
        async for item in partner_central_benefits.iter_list_benefit_allocations():
            print(item)

Error Handling

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

from capo_partnercentral_benefits import AsyncPartnerCentralBenefitsClient
from capo_partnercentral_benefits.error import AccessDeniedException


async def main():
    async with AsyncPartnerCentralBenefitsClient() as partner_central_benefits:
        try:
            await partner_central_benefits.amend_benefit_application()
        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_partnercentral_benefits import AsyncPartnerCentralBenefitsClient


async def main():
    async with AsyncPartnerCentralBenefitsClient() as partner_central_benefits:
        # Default: 3 attempts for every operation
        response = await partner_central_benefits.amend_benefit_application()

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

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

Metadata

Release files for capo-partnercentral-benefits 0.3.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-partnercentral-benefits 0.3.0
File Size Uploaded Provenance
capo_partnercentral_benefits-0.3.0.tar.gz 89.2 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-partnercentral-benefits 0.3.0
File Interpreter ABI Platform
capo_partnercentral_benefits-0.3.0-py3-none-any.whl Python 3 none any Details

Total release size: 268.2 kB

Release files / capo_partnercentral_benefits-0.3.0.tar.gz

Download URL capo_partnercentral_benefits-0.3.0.tar.gz
Size 89.2 kB
Tags Source
SHA-256 checksum
How to use checksums
26cb70c392d8c3bcef6c9eca790a7b26f1342c46499734b517ecfce1979d909e
BLAKE2b-256 checksum
How to use checksums
6b73331d3b4745aaf3433c1c0780886e1977c63e07c59c01b01f219b3470cdfa
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.22 {"installer":{"name":"uv","version":"0.12.22","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_partnercentral_benefits-0.3.0-py3-none-any.whl

Download URL capo_partnercentral_benefits-0.3.0-py3-none-any.whl
Size 179.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
87ab922bfcae91220833bae1dc3b653e5e12632f872f3f6c4212f95450e8b2ad
BLAKE2b-256 checksum
How to use checksums
0c80105e8e2c0b17763120bc51b31701520a44b59280a20e108421a26ce5b029
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.22 {"installer":{"name":"uv","version":"0.12.22","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-partnercentral-benefits 0.3.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