Create a schedule
Starts runs of one workflow of one app on a cron timetable. The caller also needs workflows.runs.start on the workflow. A repeat with the same Idempotency-Key replays the stored 201 with Idempotent-Replayed: true. Names aren't unique.
https://workflows-api.ezghcloud.com/v1/organizations/{orgId}/projects/{projectId}/schedulesAuthorization
Path parameters
Header parameters
Request bodyJSONrequired
Returns
200
The schedule this Idempotency-Key already created, once the key's stored answer has expired (48 h) and the request is the same in every field (otherwise 409 idempotency_conflict).
201
The new schedule. ETag is its revision.
400
invalid_request (with issues), invalid_cursor, or the endpoint's own 400 codes.
403
access_denied: the caller's policies don't allow the action; forbidden_origin: a cookie-authenticated write from an origin that isn't allowed; spend_limit_reached.
404
not_found: unknown, malformed, or in an organization the caller isn't in.
409
quota_exceeded (an allocation quota, with quota), idempotency_conflict, idempotency_in_progress (with Retry-After), organization_deletion_pending, operation_in_progress, or the endpoint's own 409 codes.
413
payload_too_large: the body is over the endpoint's limit (1 MiB unless it says otherwise).
429
too_many_requests, with Retry-After; or quota_exceeded (a rate, usage or concurrency quota, with quota), never with Retry-After.
500
internal_error: a bug; the details are in the logs, under the request ID.