Edit subject, preview text, or sender
The "just fix the email meta" path — no new TSX. Subject and preview-text edits are copy-on-write (a new draft version) and are auto-published when the template is already published, so the change actually sends instead of stranding a draft. The sender updates in place.
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
slug*stringTemplate slug.
application/json- body
subject?stringNew subject line.
1 <= length <= 300preview_text?stringInbox preview text (the preheader). Rewrites the template's <Preview> line. Pass "" to clear it.
length <= 300sender_id?|Sender identity for this template. null resets to the project default sender.
Meta updated. version is the new version number, or null when only the sender changed.
application/json- response
slug?stringversion?integer|nullcurl -X PATCH 'https://sendandretain.com/api/v1/templates/string/meta' \ -H 'Content-Type: application/json' \ -d '{ "subject": "Your Acme receipt", "preview_text": "Order #991 — thanks!"}'{ "slug": "welcome", "version": 3}