senderkit templates lists the templates in your
workspace and prints the detail of a single one. It’s the CLI’s window into the
dashboard — useful for confirming a slug exists before you wire up a send, or
for scripting reports against your template catalogue.
Templates are managed in the SenderKit dashboard —
copy edits, version publishes, and channel changes all happen there. The CLI
is read-only on templates; there is no
pull, push, or create command,
because templates aren’t files on disk. To create or regenerate templates
programmatically, use the MCP tools
senderkit_templates_create and
senderkit_templates_regenerate
(AI-assisted, saves as a draft for review), or the REST API
for direct writes.senderkit templates list
List every template in the workspace. No arguments, no flags.
--json returns the full template objects:
senderkit templates get
Fetch a single template by slug. Useful for confirming the published version,
its channel, or its description.
Arguments
required
Template slug, e.g.
"welcome".Examples
--json, you get the full template payload — slug, channel, status,
current version detail, timestamps, and more — matching the
GET /v1/templates/:slug response.
A template that doesn’t exist returns 404 and exits non-zero, so you can use
get as a precondition check in scripts:
Templates
The dashboard-editable definitions the CLI is reading.
Versioning
How the
version field on a template is chosen.send
Use a slug from
list to fire a real send.API Reference
The endpoints behind these commands.