Edit a step
Edits one step in place, addressed by position. Step TYPE is immutable — to change it, remove the step and add a new one. While the automation is ACTIVE only steps no run has reached yet may be edited; otherwise pause first.
bearerAuth writeAuthorizationBearer <token>An API key from the dashboard under Settings → API keys, sent as Authorization: Bearer aem_….
Authorization has two independent axes.
The scope is ranked — a key satisfies any requirement at or below its own tier:
read— see messages, contacts and metrics. Changes nothing, and cannot send.write— everythingreaddoes, plus managing templates, contacts, automations, segments and suppressions. This is what editing a template needs.admin— everythingwritedoes, plus sending configuration: domains, senders, webhook registration, kill switch, daily cap, brand.
There is no approve scope. It was a rung once; it is not one now, and a key requested with it is rejected.
The approval grant (can_approve) is a separate boolean, not a rung. Delivering mail to a real inbox needs write and the grant. Keeping them on separate axes is what makes the review gate a control rather than a convention: a key that may propose is not automatically a key that may approve its own proposal.
Give your application the lowest tier that works. Most need write and the grant — the dashboard mints that combination as Send + manage; Manage only is the same rung with the grant withheld.
Scope: write
application/json- body
automation*stringAutomation id or name.
1 <= lengthposition*integerThe step's globally-unique position within the automation.
-9007199254740991 <= value <= 9007199254740991patch*Fields to change. Keys are validated against the step's actual type.
Step updated.
application/json- response
position?integercurl -X PUT 'https://sendandretain.com/api/v1/automations/steps' \ -H 'Content-Type: application/json' \ -d '{ "automation": "Win back", "position": 2, "patch": { "subject": "One last thing", "previewText": "We saved your spot" }}'{ "position": 2}