Skip to main content

capo-xray: typed, async Python SDK for AWS Xray

capo-xray is a typed Python SDK for AWS Xray. It has an async client, AsyncXRayClient, for asyncio and trio, and a sync client, XRayClient, 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/xray/

Installation

pip install capo-xray

Usage

from capo_xray import AsyncXRayClient


async def main():
    async with AsyncXRayClient() as x_ray:
        # Example: call the batch_get_traces operation
        response = await x_ray.batch_get_traces()
        print(response["traces"])

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_xray import AsyncXRayClient


async def main():
    async with AsyncXRayClient() as x_ray:
        # Example: paginate over batch_get_traces
        async for item in x_ray.iter_batch_get_traces():
            print(item)

Error Handling

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

from capo_xray import AsyncXRayClient
from capo_xray.error import InvalidRequestException


async def main():
    async with AsyncXRayClient() as x_ray:
        try:
            await x_ray.batch_get_traces()
        except InvalidRequestException 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_xray import AsyncXRayClient


async def main():
    async with AsyncXRayClient() as x_ray:
        # Default: 3 attempts for every operation
        response = await x_ray.batch_get_traces()

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

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

Metadata

Release files for capo-xray 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-xray 0.9.0
File Size Uploaded Provenance
capo_xray-0.9.0.tar.gz 145.3 kB Without provenance Details

Built distribution (wheel)

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

Total release size: 473.8 kB

Release files / capo_xray-0.9.0.tar.gz

Download URL capo_xray-0.9.0.tar.gz
Size 145.3 kB
Tags Source
SHA-256 checksum
How to use checksums
e74f20b4fd3d1cef1ded5390c0b1024c3354040893890d11eaefeafcccb161a7
BLAKE2b-256 checksum
How to use checksums
ca341971503952128262144e0ad949bfb33a6e23a94012c1b04adfe4c9cc63f2
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_xray-0.9.0-py3-none-any.whl

Download URL capo_xray-0.9.0-py3-none-any.whl
Size 328.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
8a3f79883289620c0a64a0b835c707a70be2481de2db043b83603da4f31c55df
BLAKE2b-256 checksum
How to use checksums
10c2e7c6bf2553f5038e535756a00a1f17f9d45715d792d0f59df6f586d3ce85
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-xray 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.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

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