Skip to main content

Getting Started

Installation

pip install capo-billing

Usage

from capo_billing import AsyncBillingClient


async def main():
    async with AsyncBillingClient() as billing:
        # Example: call the associate_source_views operation
        response = await billing.associate_source_views()
        print(response["arn"])

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_billing import AsyncBillingClient


async def main():
    async with AsyncBillingClient() as billing:
        # Example: paginate over get_credit_allocation_history
        async for item in billing.iter_get_credit_allocation_history():
            print(item)

Error Handling

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

from capo_billing import AsyncBillingClient
from capo_billing.error import AccessDeniedException


async def main():
    async with AsyncBillingClient() as billing:
        try:
            await billing.associate_source_views()
        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_billing import AsyncBillingClient


async def main():
    async with AsyncBillingClient() as billing:
        # Default: 3 attempts for every operation
        response = await billing.associate_source_views()

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

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

Metadata

Release files for capo-billing 0.9.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-billing 0.9.0
File Size Uploaded Provenance
capo_billing-0.9.0.tar.gz 115.3 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-billing 0.9.0
File Interpreter ABI Platform
capo_billing-0.9.0-py3-none-any.whl Python 3 none any Details

Total release size: 349.2 kB

Release files / capo_billing-0.9.0.tar.gz

Download URL capo_billing-0.9.0.tar.gz
Size 115.3 kB
Tags Source
SHA-256 checksum
How to use checksums
8b5461ec965f2a834bd56a59600c59345e119ddcfa8dd47624a7c88d6563755a
BLAKE2b-256 checksum
How to use checksums
2ec49a62123255115803972d1dc3acb42c2affa7da3b230087360c7033d4bf20
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_billing-0.9.0-py3-none-any.whl

Download URL capo_billing-0.9.0-py3-none-any.whl
Size 233.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
33729c326a360a3144a4fdef08eb551b396274f90a75df3fe34463c3f9edc427
BLAKE2b-256 checksum
How to use checksums
ecb690652331d6b5aad20138a656d9615c0fffbdc01d2d5f974e128265b25097
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-billing 0.9.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