SMS templates
Account-token CRUD for campaign SMS templates (campaign/template/sms/*, authentication, no throttle).
Account-token CRUD for campaign SMS templates (campaign/template/sms/*, authentication, no throttle). Endpoints: create (seeds a default message body), list ({value, label} dropdown scoped to a required store_id plus company + global templates), update (content/links, optional channel wiring, copy-on-write for globals), and get-by-id (optional campaign_id to resolve the campaign's channel template with placeholders filled). Scoped to the caller's company_id; templates must belong to the caller's company or be global. Called by the campaign builder / templates UI.
Prerequisites
- A bearer token in the
Authorizationheader. Any endpoint that needs no token says so on its own page. - The id of each record the call targets. Every endpoint page lists the ids it needs.
Errors
| Status | Meaning |
|---|---|
401 | The bearer token is missing, expired or invalid |
403 | The token is valid but the record sits outside your account |
422 | The request failed validation — the response names the fields |
500 | Unexpected server error |
Individual endpoints may return more; each page lists its own.
Endpoints
GET — Get SMS templates selectable for a store as a {value, label} dropdown source: the given store's templates plus the caller company's templates plus global (both company_id and store_id NULL) templates, sorted by name.
POST — Update an existing SMS template (content, name, landing-page and review-site links).
Updated 9 days ago