Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Windmill http_trigger API

The http_trigger API from Windmill — 9 operation(s) for http_trigger.

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

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

This API exposes 9 operations across 9 paths, and defines 9 schemas. It is described by OpenAPI 3.0.3, at version 1.694.0.

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

9 operations 9 paths 9 schemas 1 DELETE3 GET5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
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 http_trigger 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 9

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

http_trigger 9
POST
/w/{workspace}/http_triggers/create_many
Create Many HTTP Triggers
createHttpTriggers 1 param body → 201
POST
/w/{workspace}/http_triggers/create
Create Http Trigger
createHttpTrigger 1 param body → 201
POST
/w/{workspace}/http_triggers/update/{path}
Update Http Trigger
updateHttpTrigger 2 params body → 200
DELETE
/w/{workspace}/http_triggers/delete/{path}
Delete Http Trigger
deleteHttpTrigger 2 params → 200
GET
/w/{workspace}/http_triggers/get/{path}
Get Http Trigger
getHttpTrigger 2 params → 200
GET
/w/{workspace}/http_triggers/list
List Http Triggers
listHttpTriggers 7 params → 200
GET
/w/{workspace}/http_triggers/exists/{path}
Does Http Trigger Exists
existsHttpTrigger 2 params → 200
POST
/w/{workspace}/http_triggers/route_exists
Does Route Exists
existsRoute 1 param body → 200
POST
/w/{workspace}/http_triggers/setmode/{path}
Enable/disable Http Trigger
setHttpTriggerMode 2 params body → 200

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are NewHttpTrigger (23 properties), EditHttpTrigger (22 properties), HttpTrigger (15 properties), TriggerExtraProperty (10 properties). Each schema is shown below with its type and property counts.

HttpTrigger
object
15 properties 8 required
HttpMethod
string
TriggerExtraProperty
object
10 properties 9 required
HttpRequestType
string
AuthenticationMethod
string
ScriptArgs
object
The arguments to pass to the script or flow
NewHttpTrigger
object
23 properties 7 required
TriggerMode
string
job trigger mode
EditHttpTrigger
object
22 properties 7 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

windmill-http-trigger-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