Autogenerated Windmill OpenApi Client

This is the raw autogenerated api client. You are most likely more interested in wmill which leverages this client to offer an user friendly experience. We use this openapi python client generator

windmill-api

A client library for accessing Windmill API

Usage

First, create a client:

from windmill_api import Client

client = Client(base_url="https://api.example.com")

If the endpoints you're going to hit require authentication, use AuthenticatedClient instead:

from windmill_api import AuthenticatedClient

client = AuthenticatedClient(base_url="https://api.example.com", token="SuperSecretToken")

Now call your endpoint and use your models:

from windmill_api.models import MyDataModel
from windmill_api.api.my_tag import get_my_data_model
from windmill_api.types import Response

with client as client:
    my_data: MyDataModel = get_my_data_model.sync(client=client)
    # or if you need more info (e.g. status_code)
    response: Response[MyDataModel] = get_my_data_model.sync_detailed(client=client)

Or do the same thing with an async version:

from windmill_api.models import MyDataModel
from windmill_api.api.my_tag import get_my_data_model
from windmill_api.types import Response

async with client as client:
    my_data: MyDataModel = await get_my_data_model.asyncio(client=client)
    response: Response[MyDataModel] = await get_my_data_model.asyncio_detailed(client=client)

By default, when you're calling an HTTPS API it will attempt to verify that SSL is working correctly. Using certificate verification is highly recommended most of the time, but sometimes you may need to authenticate to a server (especially an internal server) using a custom certificate bundle.

client = AuthenticatedClient(
    base_url="https://internal_api.example.com", 
    token="SuperSecretToken",
    verify_ssl="/path/to/certificate_bundle.pem",
)

You can also disable certificate validation altogether, but beware that this is a security risk.

client = AuthenticatedClient(
    base_url="https://internal_api.example.com", 
    token="SuperSecretToken", 
    verify_ssl=False
)

Things to know:

Every path/method combo becomes a Python module with four functions:
1. sync: Blocking request that returns parsed data (if successful) or None
2. sync_detailed: Blocking request that always returns a Request, optionally with parsed set if the request was successful.
3. asyncio: Like sync but async instead of blocking
4. asyncio_detailed: Like sync_detailed but async instead of blocking
All path/query params, and bodies become method arguments.
If your endpoint had any tags on it, the first tag will be used as a module name for the function (my_tag above)
Any endpoint which did not have a tag will be in windmill_api.api.default

Advanced customizations

There are more settings on the generated Client class which let you control more runtime behavior, check out the docstring on that class for more info. You can also customize the underlying httpx.Client or httpx.AsyncClient (depending on your use-case):

from windmill_api import Client

def log_request(request):
    print(f"Request event hook: {request.method} {request.url} - Waiting for response")

def log_response(response):
    request = response.request
    print(f"Response event hook: {request.method} {request.url} - Status {response.status_code}")

client = Client(
    base_url="https://api.example.com",
    httpx_args={"event_hooks": {"request": [log_request], "response": [log_response]}},
)

# Or get the underlying httpx client to modify directly with client.get_httpx_client() or client.get_async_httpx_client()

You can even set the httpx client directly, but beware that this will override any existing settings (e.g., base_url):

import httpx
from windmill_api import Client

client = Client(
    base_url="https://api.example.com",
)
# Note that base_url needs to be re-set, as would any shared cookies, headers, etc.
client.set_httpx_client(httpx.Client(base_url="https://api.example.com", proxies="http://localhost:8030"))

Metadata

Release files for windmill-api 1.831.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for windmill-api 1.831.0
File	Size	Uploaded	Provenance
windmill_api-1.831.0.tar.gz	2.8 MB	Oct 13, 2026	Without provenance	Details

Built distribution (wheel)

Table of built distributions (wheels) for windmill-api 1.831.0
File	Interpreter	ABI	Platform	Reset
windmill_api-1.831.0-py3-none-any.whl 8.9 MB Oct 13, 2026 Without provenance	Python 3	none	any	Details

Total release size: 11.7 MB

Release files / windmill_api-1.831.0.tar.gz

Download URL	windmill_api-1.831.0.tar.gz
Size	2.8 MB
Tags	Source
SHA-256 checksum How to use checksums	`ed74a329d5ac843bf60af19888e8109f2a6ef1f60b3aedceedcd9f3965555616`
BLAKE2b-256 checksum How to use checksums	`f2e92cc4ad4943435ffde6620cdf349e6f92cb8260539a5abf09dbe36a357061`
Upload date	Oct 13, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`poetry/1.6.1 CPython/3.11.3 Linux/6.14.0-1018-aws`

Release files / windmill_api-1.831.0-py3-none-any.whl

Download URL	windmill_api-1.831.0-py3-none-any.whl
Size	8.9 MB
Tags	Python 3
SHA-256 checksum How to use checksums	`85de2515bea5ca3e431d87bfea659b4fcd3765799b7c3e2069445222fc24dd81`
BLAKE2b-256 checksum How to use checksums	`39010beba6177c311ae5ffd742fc94af00780e5a2dcfcebf88606351a08370fd`
Upload date	Oct 13, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`poetry/1.6.1 CPython/3.11.3 Linux/6.14.0-1018-aws`

Security for windmill-api 1.831.0

Report project as malware

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.