HealthCloud SDK for Python
Typed access to HealthCloud platform APIs and connector clients from Python applications.
Requires Python 3.13 or newer. Python 3.9–3.12 are no longer supported.
Installation
python -m pip install healthcloud-sdk
Quick start
from healthcloud import HCSDK
with HCSDK(
environment="dev",
tenant_id="<TENANT_ID>",
) as sdk:
# Select a service client from sdk.
pass
Authentication
Public authentication calls use the configured tenant. For authenticated APIs, initialize with access_token or call sdk.set_access_token(token). Never commit tokens or credentials.
Detailed documentation
See docs/index.md for method-centric API, model, configuration, authentication, and example documentation. Detailed pages are generated from the shared structured docs data; this README intentionally remains package-level.
Package overview
The SDK exposes service clients from one HCSDK instance. The generated docs index lists operations only when stable contract metadata is available.
1 maintainer
Metadata
1 maintainer
Release files for healthcloud-sdk 3.13.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 | |
|---|---|---|---|---|
| healthcloud_sdk-3.13.0.tar.gz | 1.6 MB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| healthcloud_sdk-3.13.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 8.8 MB
Release files / healthcloud_sdk-3.13.0.tar.gz
| Download URL | healthcloud_sdk-3.13.0.tar.gz |
|---|---|
| Size | 1.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c176c09dae96d4b33d645cbb114cfb9836f0c510ed21d7f159baccf6e5e57b04
|
|
BLAKE2b-256 checksum How to use checksums |
5d594e8bb6261aa75745f39dd5e4f95604c72a7cb12221b3b9a3a63d5b8a7156
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / healthcloud_sdk-3.13.0-py3-none-any.whl
| Download URL | healthcloud_sdk-3.13.0-py3-none-any.whl |
|---|---|
| Size | 7.2 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
913f56c0a33d795b3090c246d745f04f0db8d03d0baaec9fadfa35de4328f077
|
|
BLAKE2b-256 checksum How to use checksums |
2c932ba8f2b35a80a23361c1148d09ed9a47fe308ef513b3299b82c2cf7a2ec7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logSecurity for healthcloud-sdk 3.13.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for healthcloud_sdk-3.13.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logA 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.
