Getting Started
Installation
pip install capo-chime-sdk-meetings
Usage
from capo_chime_sdk_meetings import AsyncChimeSDKMeetingsClient
async def main():
async with AsyncChimeSDKMeetingsClient() as chime_sdk_meetings:
# Example: call the batch_create_attendee operation
response = await chime_sdk_meetings.batch_create_attendee()
print(response["attendees"])
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_chime_sdk_meetings import AsyncChimeSDKMeetingsClient
async def main():
async with AsyncChimeSDKMeetingsClient() as chime_sdk_meetings:
# Example: paginate over list_attendees
async for item in chime_sdk_meetings.iter_list_attendees():
print(item)
Error Handling
The SDK raises exceptions for errors returned by the API. Catch them to handle failures gracefully.
from capo_chime_sdk_meetings import AsyncChimeSDKMeetingsClient
from capo_chime_sdk_meetings.error import BadRequestException
async def main():
async with AsyncChimeSDKMeetingsClient() as chime_sdk_meetings:
try:
await chime_sdk_meetings.batch_create_attendee()
except BadRequestException 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_chime_sdk_meetings import AsyncChimeSDKMeetingsClient
async def main():
async with AsyncChimeSDKMeetingsClient() as chime_sdk_meetings:
# Default: 3 attempts for every operation
response = await chime_sdk_meetings.batch_create_attendee()
# Override per operation
response = await chime_sdk_meetings.batch_create_attendee(config_overrides={"retry_max_attempts": 5})
# Disable retries for this call
response = await chime_sdk_meetings.batch_create_attendee(config_overrides={"retry_max_attempts": 1})
Metadata
Release files for capo-chime-sdk-meetings 0.3.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_chime_sdk_meetings-0.3.0.tar.gz | 92.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| capo_chime_sdk_meetings-0.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 263.3 kB
Release files / capo_chime_sdk_meetings-0.3.0.tar.gz
| Download URL | capo_chime_sdk_meetings-0.3.0.tar.gz |
|---|---|
| Size | 92.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f078b3652535d24e953eebc7420f9b081264d8b689458cafcba9171681b2e305
|
|
BLAKE2b-256 checksum How to use checksums |
ce708644389cc4947c8bf912097e887b8125cf2e1f7de53e1dbf058b202e42c9
|
| 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_chime_sdk_meetings-0.3.0-py3-none-any.whl
| Download URL | capo_chime_sdk_meetings-0.3.0-py3-none-any.whl |
|---|---|
| Size | 170.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8146f4801a65275e7ade9a69f317cb60d15b72bd1a7816d42d8475273b476200
|
|
BLAKE2b-256 checksum How to use checksums |
1055cd636ea92c9cbde00b59f1cd940ab91134f0d7722206e80084a14b7dcc91
|
| 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-chime-sdk-meetings 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.