Retrieve a marketing template version
One immutable snapshot, byte for byte as it was published. THIS IS THE ROUTE THAT ANSWERS “WHAT DID THAT CAMPAIGN ACTUALLY SEND”: a campaign records the version id it rendered, and this resolves it however many times the merchant has rewritten the template since. Nothing can change this row. The version table is append-only, there is no write that touches it, and the database role serving this API holds no UPDATE or DELETE grant on it. THE VERSION IS ADDRESSED UNDER ITS PARENT and the parent is part of the lookup, not decoration: a version id belonging to a different template of the same store is a 404 here rather than a body from the wrong message.
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.
Response
Success
