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 list_billing_views
        async for item in billing.iter_list_billing_views():
            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.1.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.1.0
File Size Uploaded Provenance
capo_billing-0.1.0.tar.gz 69.1 kB Without provenance Details

Built distribution (wheel)

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

Total release size: 196.6 kB

Release files / capo_billing-0.1.0.tar.gz

Download URL capo_billing-0.1.0.tar.gz
Size 69.1 kB
Tags Source
SHA-256 checksum
How to use checksums
f3ca4b10ba5952d5de0f0d1960e4f99865acc03fa9f290b1221aaa6900695812
BLAKE2b-256 checksum
How to use checksums
b703b16ce56d5123c523d7fb969c8aeac3215e8a7119475ad037c4ab19417627
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.15 {"installer":{"name":"uv","version":"0.12.15","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.1.0-py3-none-any.whl

Download URL capo_billing-0.1.0-py3-none-any.whl
Size 127.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
e2495f528cbb2299c6642346de2e285f466b3a7e85ed18ff3e884b8b06486c6a
BLAKE2b-256 checksum
How to use checksums
532ebce598902a620ad327c9b2d3a5aafee940890d062701af0b0b186796bce4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.15 {"installer":{"name":"uv","version":"0.12.15","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.1.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