Removes the binding between the trigger and an agent
Unbinds the trigger from an agent so the agent no longer runs when the trigger fires. The call is idempotent: removing a binding that does not exist still succeeds with 204. Neither the trigger nor the agent is deleted.
Authorization
Bearer JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
Path Parameters
The trigger identifier.
uuidThe agent identifier to unbind.
The tenant identifier
Response Body
curl -X DELETE "https://api.fruxon.com/v1/tenants/string/triggers/497f6eca-6276-4993-bfeb-53cbbbba6f08/bindings/string"{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}Creates a new trigger in an Application and optionally binds it to agents atomically.
Creates the trigger together with any initial agent bindings supplied in the request, in a single transaction. The trigger `Kind` (schedule, webhook, or integration event) is fixed at creation — changing it later requires recreating the trigger, since each kind carries its own configuration shape. The owning Application is the `network` path segment. Every trigger belongs to exactly one, and an unowned trigger would be listed by no Application while still firing, so ownership is part of the address rather than an omittable body field. The created trigger is read and edited on the flat `{tenant}/triggers/{trigger}` tree, which is where the Location header points.
Adds (or returns the existing) binding between the trigger and an agent.
Binds the trigger to an agent so the agent runs whenever the trigger fires. The call is idempotent: an existing binding is returned unchanged rather than duplicated. Returns 404 when the trigger does not exist.