Triggers
Rotate an email trigger
Rotate an email trigger.
Mints a successor with the same settings, then revokes the old token. A failure in between leaves both live, never neither.
Authorizations
Authorization: Bearer ozk_…. ozk_ platform API key (Authorization: Bearer ozk_…)Path parameters
Body
application/jsontext/yaml
Available options: json, yaml, markdown, text
Response
The successor (secret shown once), with rotated = the revoked token Response format negotiates via the format field, an Accept header (application/json, text/yaml, text/markdown, text/plain), or the request Content-Type mirror; default JSON.
application/jsontext/yamltext/markdowntext/plain
invalid_json — body is not valid JSON
application/json
unauthorized — missing, invalid or revoked ozk_ key
application/json
trigger_not_found — no such trigger on this schedule; schedule_not_found — no schedule with that id for this key; not_found — no route for this method on this path: every other method answers it
application/json
invalid_params — a field is missing or malformed (the envelope names it); nothing was written
application/json
scheduler_error — the scheduler failed or did not answer; no detail is returned, retry
application/json