Skip to main content

Getting Started

Installation

pip install capo-connectcampaignsv2

Usage

from capo_connectcampaignsv2 import AsyncConnectCampaignsV2Client


async def main():
    async with AsyncConnectCampaignsV2Client() as connect_campaigns_v2:
        # Example: call the create_campaign operation
        response = await connect_campaigns_v2.create_campaign()
        print(response["id"])

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_connectcampaignsv2 import AsyncConnectCampaignsV2Client


async def main():
    async with AsyncConnectCampaignsV2Client() as connect_campaigns_v2:
        # Example: paginate over list_campaigns
        async for item in connect_campaigns_v2.iter_list_campaigns():
            print(item)

Error Handling

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

from capo_connectcampaignsv2 import AsyncConnectCampaignsV2Client
from capo_connectcampaignsv2.error import AccessDeniedException


async def main():
    async with AsyncConnectCampaignsV2Client() as connect_campaigns_v2:
        try:
            await connect_campaigns_v2.create_campaign()
        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_connectcampaignsv2 import AsyncConnectCampaignsV2Client


async def main():
    async with AsyncConnectCampaignsV2Client() as connect_campaigns_v2:
        # Default: 3 attempts for every operation
        response = await connect_campaigns_v2.create_campaign()

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

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

Metadata

Release files for capo-connectcampaignsv2 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-connectcampaignsv2 0.3.0
File Size Uploaded Provenance
capo_connectcampaignsv2-0.3.0.tar.gz 100.2 kB Without provenance Details

Built distribution (wheel)

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

Total release size: 358.3 kB

Release files / capo_connectcampaignsv2-0.3.0.tar.gz

Download URL capo_connectcampaignsv2-0.3.0.tar.gz
Size 100.2 kB
Tags Source
SHA-256 checksum
How to use checksums
5c7ae1a2e16615fc29e6ba54912fcdb2585d8d531e5ad7d8142c3c5c0d74d056
BLAKE2b-256 checksum
How to use checksums
c87fb47b8fe5f080bc20eca44527550a2475fce40c20c9f033253d9a12e91ed9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.18 {"installer":{"name":"uv","version":"0.12.18","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_connectcampaignsv2-0.3.0-py3-none-any.whl

Download URL capo_connectcampaignsv2-0.3.0-py3-none-any.whl
Size 258.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
2ce3f278223e6158f2d8842e2c8bf02e1f9085fd9c2cdb490db5254f768f4487
BLAKE2b-256 checksum
How to use checksums
5fd14a5efffbdf6bfbdcb317def67c8f7ba74719b0487e7733fa3f48b8d47b01
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.18 {"installer":{"name":"uv","version":"0.12.18","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-connectcampaignsv2 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