Retire a template, keeping its published versions
Retires a template. THIS IS WHAT THIS FAMILY PUBLISHES INSTEAD OF A DELETE, and there is no delete anywhere on it: a delivered message resolves its copy through a published version, so a deletable version would strand one. An archived template stops being sendable while every published version stays readable and renderable, so campaign history keeps resolving. restore is the exact inverse, which is what makes this safe to hand an integration.
Authorizations
A secret API key. Publishable keys cannot reach this API. A key may carry an expiry, and an expired key is refused exactly like an unknown one, with a 401 that names no reason; check the key's expires_at in the dashboard rather than inferring it from a response. When a merchant rolls a key's secret they choose a grace window of up to 3 days, and for its duration BOTH the new secret and the one it replaced authenticate, so an integration moves over on its own deploy schedule instead of at the instant the button is pressed. Move before the window closes: after it, the old secret is refused. Nothing else about this contract moves with a roll. The key keeps its id and its scopes, so the only thing an integration updates is the credential itself.
Headers
A unique key per logical write. Replaying a request with the same key returns the first response byte for byte instead of applying the write twice.
Path Parameters
Body
Takes no parameters, and an empty body is expected. The response is the template with status archived, which is the proof it is no longer sendable. restore is the exact inverse, which is why this is a POST and not a DELETE.
Response
Success
