Removes one of an automation's spend limits
Any of an automation's limits can be removed; removing one that is not set does nothing. The automation's runs and what they cost are unaffected, and its agents' own limits still apply.
Authorization
Bearer JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
Path Parameters
The automation (trigger) identifier.
uuidThe tenant identifier
Query Parameters
The window: MONTHLY (default), WEEKLY or DAILY.
"MONTHLY""UNSPECIFIED" | "DAILY" | "WEEKLY" | "MONTHLY"Response Body
curl -X DELETE "https://api.fruxon.com/v1/tenants/string/triggers/497f6eca-6276-4993-bfeb-53cbbbba6f08/budget"{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}Lists every spend limit an automation has — at most one per window.
Shortest window first. Empty for an automation nobody has set a limit on: automations get none by default, unlike agents. The whole set is one page.
Sets one of an automation's spend limits
Creates the limit for the window in the body (default `MONTHLY`), or replaces the amount, thresholds and enforce flag of the one already there. A daily, a weekly and a monthly limit can coexist, and must stay ordered daily ≤ weekly ≤ monthly. A new limit enforces and alerts at 80% and 100% unless the body says otherwise; `enforceLimit: false` makes it alert only. Spend already made in the current window counts against a new limit from the moment runs recording it settle; the limit does not reach back over runs before it existed.