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.7.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.7.0
File Size Uploaded Provenance
capo_partnercentral_benefits-0.7.0.tar.gz 93.7 kB Without provenance Details

Built distribution (wheel)

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

Total release size: 277.8 kB

Release files / capo_partnercentral_benefits-0.7.0.tar.gz

Download URL capo_partnercentral_benefits-0.7.0.tar.gz
Size 93.7 kB
Tags Source
SHA-256 checksum
How to use checksums
73216f563da05f6bbc56f3cc027997a2ca0681a4d38936c391c9bd81428dbf1a
BLAKE2b-256 checksum
How to use checksums
e8e43fb12d7120a2d2688db5fa4117bcd8904a48ced0414e1a8bc061485f116d
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_partnercentral_benefits-0.7.0-py3-none-any.whl

Download URL capo_partnercentral_benefits-0.7.0-py3-none-any.whl
Size 184.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
14fe8cc483376ac288f03b90e82b2dc13423ab23766a813b6f5e397430896700
BLAKE2b-256 checksum
How to use checksums
53915af11e8be82aab199072cb48d7975f649c3ae3009585ec5491b9185c2d3c
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-partnercentral-benefits 0.7.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