Skip to main content

capo-marketplace-reporting: typed, async Python SDK for AWS Marketplace Reporting

capo-marketplace-reporting is a typed Python SDK for AWS Marketplace Reporting. It has an async client, AsyncMarketplaceReportingClient, for asyncio and trio, and a sync client, MarketplaceReportingClient, with the same methods. Requests and responses are typed with TypedDicts, so your editor and type checker know every field.

It is part of capo, a community-driven alternative to boto3 and aioboto3, built on its own HTTP stack instead of botocore and generated from the official AWS Smithy models. Documentation: https://capo-sdk.dev/services/marketplace-reporting/

Installation

pip install capo-marketplace-reporting

Usage

from capo_marketplace_reporting import AsyncMarketplaceReportingClient


async def main():
    async with AsyncMarketplaceReportingClient() as marketplace_reporting:
        # Example: call the get_buyer_dashboard operation
        response = await marketplace_reporting.get_buyer_dashboard()
        print(response["embed_url"])

Error Handling

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

from capo_marketplace_reporting import AsyncMarketplaceReportingClient
from capo_marketplace_reporting.error import AccessDeniedException


async def main():
    async with AsyncMarketplaceReportingClient() as marketplace_reporting:
        try:
            await marketplace_reporting.get_buyer_dashboard()
        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_marketplace_reporting import AsyncMarketplaceReportingClient


async def main():
    async with AsyncMarketplaceReportingClient() as marketplace_reporting:
        # Default: 3 attempts for every operation
        response = await marketplace_reporting.get_buyer_dashboard()

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

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

Metadata

Release files for capo-marketplace-reporting 0.8.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-marketplace-reporting 0.8.0
File Size Uploaded Provenance
capo_marketplace_reporting-0.8.0.tar.gz 59.2 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-marketplace-reporting 0.8.0
File Interpreter ABI Platform
capo_marketplace_reporting-0.8.0-py3-none-any.whl Python 3 none any Details

Total release size: 126.2 kB

Release files / capo_marketplace_reporting-0.8.0.tar.gz

Download URL capo_marketplace_reporting-0.8.0.tar.gz
Size 59.2 kB
Tags Source
SHA-256 checksum
How to use checksums
e71a9cb1ee1d9cd47a7bc61df09789cabdeab6771ca64bbd04d8273e626b43d0
BLAKE2b-256 checksum
How to use checksums
b3ed8a0b7890aac3a99e6a9ce72af4170cd915b7c2ec9616b657cdb9f161617b
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_marketplace_reporting-0.8.0-py3-none-any.whl

Download URL capo_marketplace_reporting-0.8.0-py3-none-any.whl
Size 67.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
fc5f5665f757938169f653f003b9a326066528c160462833fcf4925b0c2eaf6e
BLAKE2b-256 checksum
How to use checksums
a9cd22c73c27006d319c08b30d9d8803e2e966f0ceb2bfa186caa139244c1af3
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-marketplace-reporting 0.8.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