hotcodepush
The typed Python client for the HotCodePush REST API, the over-the-air (OTA) update platform for React Native, Expo, Capacitor and Cordova.
Installation
pip install hotcodepush
Or with uv:
uv add hotcodepush
It requires Python 3.11 or later.
Usage
from hotcodepush import HotCodePush
hot_code_push = HotCodePush() # reads the API token from HOTCODEPUSH_TOKEN
organization, *_ = hot_code_push.organizations.list()
app = hot_code_push.organizations.apps.create(
framework="capacitor", name="Demo", organization_id=organization.id
)
channel = hot_code_push.apps.channels.create(app_id=app.id, name="staging")
hot_code_push.apps.channels.pause(app_id=app.id, channel_id=channel.id)
The resources mirror the API's paths, /v1/apps/{appId}/channels being apps.channels.
Every method takes keyword arguments and returns pydantic models with snake_case fields.
An optional argument you leave out stays out of the request; None sends null, which clears a field such as a channel's expires_at.
users.get(user_id="me") answers the caller behind the token, as me addresses the caller wherever the API takes a {userId}.
An upload takes bytes or a file object with its content_length, and streams it.
Bytes above 64 MiB go up in parts, and a retry sends them again; a file object is read once, so a failed upload of one is not retried.
Creating an organization, an invitation, an app, a channel, a release, a rollback, a bundle or a binary sends an Idempotency-Key, a UUID per call kept across the client's own retries; pass idempotency_key to reuse one when you retry the call yourself, and the API answers the first result again for 24 hours.
A failed request raises a HotCodePushError with the API's code, message and details and the HTTP status.
Documentation
The documentation lives at hotcodepush.com/docs/api/python.
Development
uv sync
uv run ruff format --check .
uv run ruff check .
uv run mypy
uv run pytest
uv build
uv run ruff format . formats the code.
License
See LICENSE.
Metadata
Release files for hotcodepush 0.2.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 | |
|---|---|---|---|---|
| hotcodepush-0.2.0.tar.gz | 119.1 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| hotcodepush-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 178.1 kB
Release files / hotcodepush-0.2.0.tar.gz
| Download URL | hotcodepush-0.2.0.tar.gz |
|---|---|
| Size | 119.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
12d4cec86308d772ad39609b84ca114ff70636f71a65296177c98a4cb3369f27
|
|
BLAKE2b-256 checksum How to use checksums |
3f9df2e9198aeebf721c184dc20ad9bb37c2cbb6325c30d4cb0047ca34ce2741
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 26, 2026.
Transparency logRelease files / hotcodepush-0.2.0-py3-none-any.whl
| Download URL | hotcodepush-0.2.0-py3-none-any.whl |
|---|---|
| Size | 59.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
841926f51e9877089660e336151ad8660f8e84849e8cc6d7f6e8a4d94c8a5ff2
|
|
BLAKE2b-256 checksum How to use checksums |
70b9b18cb2cf4f5d275030908675fceb0c33ca08039a5a7fb5642066d3a50c0c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 26, 2026.
Transparency logSecurity for hotcodepush 0.2.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 hotcodepush-0.2.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 26, 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.