infrawrench-sdk
Generated Python client for the Infrawrench API (API version 1.58.0).
Do not edit this package by hand — it is regenerated from openapi.json and
is not checked into the repository. Run
pnpm --filter @infrawrench/web generate:sdk to rebuild it; the generator lives
in app/packages/web/scripts/sdk.
Install
pip install infrawrench-sdk
Requires Python 3.9+ and nothing else: the client is built on
urllib.request and json from the standard library.
Usage
import os
from infrawrench_sdk import APIV1Client, ApiError
client = APIV1Client(
api_key=os.environ["INFRAWRENCH_API_KEY"],
org_id=os.environ["INFRAWRENCH_ORG_ID"],
)
try:
accounts = client.accounts.list()
except ApiError as error:
print(error.status, error.code, error.body)
Calls are namespaced to mirror the URL structure, so
POST /api/org/{orgId}/accounts/{id}/sync is client.accounts.sync(id=...).
Every argument is keyword-only. Set org_id once on the client and every
org-scoped call can omit it; pass org_id= on an individual call to
override it there.
Every method also takes request_options=RequestOptions(...) for per-call
headers and timeout. Non-2xx responses raise ApiError, which carries
status, the parsed body, and the machine-readable code when the API sends
one.
Types
Models are TypedDicts, so responses are ordinary dicts and request bodies can
be written as literals:
client.resources.secret_versions.add(
plugin_id="aws",
type_id="s3_bucket",
body={"resourceId": resource_id, "value": "..."},
)
The package ships py.typed (PEP 561), so mypy and pyright check those calls
against the spec without a stub package.
Scope
This package covers the published API surface only. Operations marked
x-internal in the spec — the admin surface, webhook receivers, desktop sync,
push registration, and the browser auth redirects — are not generated.
License
MIT — see LICENSE. Copyright (c) 2026 Infrawrench LLC.
Note that this client is more permissively licensed than the service it talks to: the Infrawrench source is BUSL-1.1, but the generated clients are MIT so you can link one into your own software without inheriting those terms.
Metadata
Release files for infrawrench-sdk 1.58.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 | Actions |
|---|---|---|---|---|
| infrawrench_sdk-1.58.0.tar.gz | 221.9 kB | With provenance | Details for infrawrench_sdk-1.58.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| infrawrench_sdk-1.58.0-py3-none-any.whl | Python 3 | none | any | Details for infrawrench_sdk-1.58.0-py3-none-any.whl |
Total release size: 447.5 kB
Release files / infrawrench_sdk-1.58.0.tar.gz
| Download URL | infrawrench_sdk-1.58.0.tar.gz |
|---|---|
| Size | 221.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2271a7d164980337c719cc8987f76e38e3a80d960656d06454c76c6dcfa9e7a4
|
|
BLAKE2b-256 checksum How to use checksums |
7db60791ad86e735276e61d4cec543ba0f0d4331df662ecf5eac8981810b0dae
|
| 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 5, 2026.
Transparency logRelease files / infrawrench_sdk-1.58.0-py3-none-any.whl
| Download URL | infrawrench_sdk-1.58.0-py3-none-any.whl |
|---|---|
| Size | 225.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7332611df2552841526f8398f7285ff24577ba74894f1f41d3691d3c373d1194
|
|
BLAKE2b-256 checksum How to use checksums |
4517e0cd251c5ee6635137a969ac49ca087fac5bbdf71921919067f5656bc92a
|
| 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 5, 2026.
Transparency logSecurity for infrawrench-sdk 1.58.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 infrawrench_sdk-1.58.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 5, 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.