Retrieve a marketing template
One template, working copy included. html_body and text_body come back verbatim, byte for byte as stored, which is what makes the replace safe to build on: read this, change one field, send the whole thing back. WHAT YOU READ HERE IS NOT NECESSARILY WHAT WENT OUT. For the copy a campaign actually sent, follow current_version_id to the version read below, or use the version id the campaign itself recorded.
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.
Path Parameters
Response
Success
