capo-b2bi: typed, async Python SDK for AWS B2Bi
capo-b2bi is a typed Python SDK for AWS B2Bi. It has an async client, Asyncb2biClient, for asyncio and trio, and a sync client, b2biClient, 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/b2bi/
Installation
pip install capo-b2bi
Usage
from capo_b2bi import Asyncb2biClient
async def main():
async with Asyncb2biClient() as b2bi:
# Example: call the create_starter_mapping_template operation
response = await b2bi.create_starter_mapping_template()
print(response["mapping_template"])
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_b2bi import Asyncb2biClient
async def main():
async with Asyncb2biClient() as b2bi:
# Example: paginate over list_capabilities
async for item in b2bi.iter_list_capabilities():
print(item)
Error Handling
The SDK raises exceptions for errors returned by the API. Catch them to handle failures gracefully.
from capo_b2bi import Asyncb2biClient
from capo_b2bi.error import AccessDeniedException
async def main():
async with Asyncb2biClient() as b2bi:
try:
await b2bi.create_starter_mapping_template()
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_b2bi import Asyncb2biClient
async def main():
async with Asyncb2biClient() as b2bi:
# Default: 3 attempts for every operation
response = await b2bi.create_starter_mapping_template()
# Override per operation
response = await b2bi.create_starter_mapping_template(config_overrides={"retry_max_attempts": 5})
# Disable retries for this call
response = await b2bi.create_starter_mapping_template(config_overrides={"retry_max_attempts": 1})
Metadata
Release files for capo-b2bi 0.12.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| capo_b2bi-0.12.0.tar.gz | 142.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| capo_b2bi-0.12.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 426.5 kB
Release files / capo_b2bi-0.12.0.tar.gz
| Download URL | capo_b2bi-0.12.0.tar.gz |
|---|---|
| Size | 142.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3c2e2de770fca5dd006f276cd117ea58a9f2e81c894da258ecd8626fb3235947
|
|
BLAKE2b-256 checksum How to use checksums |
55aa18ae478303507c13b0ff7120927304e34fa97f96d7d11b6287190ee8ae90
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.5 {"installer":{"name":"uv","version":"0.13.5","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_b2bi-0.12.0-py3-none-any.whl
| Download URL | capo_b2bi-0.12.0-py3-none-any.whl |
|---|---|
| Size | 284.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
284b30c767e13b68977a97cff04e87ea57c78690ead45cff30e68206e7dc5f7d
|
|
BLAKE2b-256 checksum How to use checksums |
ef2e1c08af8499e3b7ddac191c80cf95a7cc4f5e2705076e2f075f54bec4b496
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.5 {"installer":{"name":"uv","version":"0.13.5","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-b2bi 0.12.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.