Save automation
Creates a monitoring automation from the spec in automation, or updates an existing one when automationId is given. On create the spec must be complete (name, actionLevel, actions, frequency, apiOutageAction, rules); on update only the fields you pass are changed.
bearerAuthAuthorizationBearer <token>An organization API key (koast_sk_…) with the API surface enabled, or an OAuth access token issued by Koast (koast_at_…) whose audience covers this API. REST access requires an active Agency plan.
brandId*integerThe brand the request acts on. Every brand-scoped resource lives under its brand.
Idempotency-Key?stringRetrying with the same key within 24 hours returns the first response without acting again.
length <= 255application/json- body
automationId?string^[1-9]\d*$1 <= lengthautomation*Whole monitoring automation spec: { name, actionLevel, actions[], frequency, apiOutageAction, rules[], campaignIds?, status?, applyToNewCampaigns? }
Save automation
application/json- response
[key: string]?unknowncurl -X POST "https://example.com/v1/brands/0/automations" \ -H "Authorization: Bearer koast_sk_..." \ -H "Content-Type: application/json" \ -d '{ "automation": { "property1": null, "property2": null } }'{ "property1": null, "property2": null}Required scope: write. CLI: koast save-automation, see Automations commands. Authentication, headers, errors and pagination work the same on every operation. See Conventions.