Batch workflow schedules
Delete many workflow schedules at once, exactly as deleteWorkflowSchedule deletes one: they stop firing and their runs keep them as owner. The manual runs schedule and a campaign’s canonical schedule are refused with CONFLICT (delete the campaign instead). Permission is checked once for the batch (the same permission as the single delete); a 403 fails the whole call. Then every id is processed in ONE transaction and the call returns HTTP 200 with one result per id, in request order: applied (removed by this call), noop (already removed) or failed (left unchanged, with error.code NOT_FOUND for an id outside this team or CONFLICT for a row a business rule protects), plus outcome counts. Read each item rather than the HTTP status. At most 100 unique ids per call.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Team (workspace) id (UUID). Discover ids via the list teams endpoint or the agent context.
Body
The action applied to every listed id. delete removes each row exactly as the single delete endpoint does.
delete an array of at most 100 item(s)
1 - 100 elementsa Universally Unique Identifier
^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$