How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Windmill input API

The input API from Windmill — 6 operation(s) for input.

Windmill input API is one of 59 APIs that Windmill publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Input. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a getting-started guide, and authentication docs.

This API exposes 6 operations across 6 paths, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version 1.694.0.

Requests are made against a single base URL, /api.

6 operations 6 paths 4 schemas 3 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.694.0
Base URL
https://app.windmill.dev/api
Authentication
HTTP Bearer, API Key
License
Resource Areas
1

Authentication & Security 2

Windmill input API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). An API key is passed in the cookie as token (cookieAuth). By default, every request must be authenticated.

Paths & Operations 6

Across 6 paths, the API surfaces 6 operations — 3 GET, 3 POST. Each is listed below with its method, path, parameters, and response codes.

input 6
GET
/w/{workspace}/inputs/history
List Inputs Used in Previously Completed Jobs
getInputHistory 7 params → 200
GET
/w/{workspace}/inputs/{jobOrInputId}/args
Get Args from History or Saved Input
getArgsFromHistoryOrSavedInput 4 params → 200
GET
/w/{workspace}/inputs/list
List Saved Inputs for a Runnable
listInputs 5 params → 200
POST
/w/{workspace}/inputs/create
Create an Input for Future Use in a Script or Flow
createInput 3 params body → 201
POST
/w/{workspace}/inputs/update
Update an Input
updateInput 1 param body → 201
POST
/w/{workspace}/inputs/delete/{input}
Delete a Saved Input
deleteInput 2 params → 200

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are Input (6 properties), UpdateInput (3 properties), CreateInput (2 properties). Each schema is shown below with its type and property counts.

CreateInput
object
2 properties 3 required
RunnableType
string
UpdateInput
object
3 properties 3 required
Input
object
6 properties 6 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

windmill-input-api-openapi.yml Raw ↑

Other APIs Windmill publishes across the network.

Windmill admin API
Windmill agent_workers API
Windmill app API
Windmill asset API
Windmill audit API
Windmill azure_trigger API
Windmill capture API
Windmill concurrencyGroups API
Windmill config API
Windmill documentation API
Windmill draft API
Windmill email_trigger API
Where this information came from

This is an independent, third-party profile of Windmill input API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.