Campaigns

PUT /v1/campaigns/templates/{templateId}

Edit a campaign template.

All Campaigns endpoints

All developer docs →

Authentication

Send an API key as a bearer token. The endpoint checks campaigns.view; a key without it is refused with 403, not 404.

Where your organisation id goes

This endpoint takes org_id as a field in the JSON body.

Your organisation id is on the API keys screen in your dashboard, beside the key itself. It is the same id in every call you make.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

curl -X PUT https://api.zinndigital.com/v1/campaigns/templates/{templateId} \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "name": <string>, "subject": <string>, "body": <string> }'

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

Editing the copy marks every locale stale and re-translates it, so a template and its 58 translations cannot drift.

Parameters

NameTypeRequiredWhat it is
templateId (path)stringYes—

Request body

NameTypeRequiredWhat it is
fallbacksbooleanNoPreview only. Render with NO merge values, so every tag falls back and the author reads what a customer we know nothing about reads. It exists because a normal preview substitutes…
namestringYes—
subjectstringYes—
bodystringYes—
purposestring<marketing, transactional>No—
channelsstring<email, in_app, slack, telegram>[]No—
org_idstringNo—

Response

NameTypeRequiredWhat it is
idstringYes—
org_idstringYes—
namestringYes—
purposestring<marketing, transactional>Yes—
subjectstringYes—
bodystringYes—
channelsstring[]Yes—
archivedbooleanYes—
created_atstringYes—
updated_atstringYes—

Errors this endpoint can return

401 · 403 · 404 · 422