Skip to main content

Getting Started

Installation

pip install capo-pinpoint-email

Usage

from capo_pinpoint_email import AsyncPinpointEmailClient


async def main():
    async with AsyncPinpointEmailClient() as pinpoint_email:
        # Example: call the create_configuration_set operation
        response = await pinpoint_email.create_configuration_set()
        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_pinpoint_email import AsyncPinpointEmailClient


async def main():
    async with AsyncPinpointEmailClient() as pinpoint_email:
        # Example: paginate over get_dedicated_ips
        async for item in pinpoint_email.iter_get_dedicated_ips():
            print(item)

Error Handling

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

from capo_pinpoint_email import AsyncPinpointEmailClient
from capo_pinpoint_email.error import AlreadyExistsException


async def main():
    async with AsyncPinpointEmailClient() as pinpoint_email:
        try:
            await pinpoint_email.create_configuration_set()
        except AlreadyExistsException 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_pinpoint_email import AsyncPinpointEmailClient


async def main():
    async with AsyncPinpointEmailClient() as pinpoint_email:
        # Default: 3 attempts for every operation
        response = await pinpoint_email.create_configuration_set()

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

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

Metadata

Release files for capo-pinpoint-email 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-pinpoint-email 0.7.0
File Size Uploaded Provenance
capo_pinpoint_email-0.7.0.tar.gz 135.7 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-pinpoint-email 0.7.0
File Interpreter ABI Platform
capo_pinpoint_email-0.7.0-py3-none-any.whl Python 3 none any Details

Total release size: 442.5 kB

Release files / capo_pinpoint_email-0.7.0.tar.gz

Download URL capo_pinpoint_email-0.7.0.tar.gz
Size 135.7 kB
Tags Source
SHA-256 checksum
How to use checksums
2c1bad5dc7e568e1fed3631dc8c9b4c1db7ee41ab22743cdfdafce4f753dbcb0
BLAKE2b-256 checksum
How to use checksums
fb311403795b7cc0de80c95e933654a62cd490d0af19f9f1033c6043ba2176fb
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_pinpoint_email-0.7.0-py3-none-any.whl

Download URL capo_pinpoint_email-0.7.0-py3-none-any.whl
Size 306.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
2c33aa011664803e9e86ce9e32362656e84cbf18cec975cd261523c85f2696f7
BLAKE2b-256 checksum
How to use checksums
4aec186dba5f4502ad91a4ae667562d4d2f81bdb108c42573d5eb068db184615
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-pinpoint-email 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