Content Templates

Content templates are server-rendered graphics — memes, quote cards, before/after comparisons, announcements, testimonials, and reaction images — that you fill in with your own text, colors, and images. Rendered images land in your media library automatically, ready to attach to a post.

Available categories

Category slug	Template
`meme`	Classic meme (top-text / bottom-text)
`quote_card`	Branded quote card
`before_after`	Side-by-side comparison
`reaction`	Reaction image
`announcement`	Product or news announcement card
`testimonial`	Customer testimonial card

templates:list

Browse available templates, optionally filtered by category.

so-me templates:list [options]

Option	Description
`--category <name>`	Filter by category (see slugs above)
`--page <number>`	Page number (default: 1)
`--limit <number>`	Items per page (default: 20)

Examples

# Every active template
so-me templates:list

# Only quote cards
so-me templates:list --category quote_card

# Compact table
so-me templates:list --table

# Just the IDs
so-me templates:list | jq -r '.data[].id'

templates:get

Fetch a template by ID, including its fields[] schema — use this to see what inputs the template expects (labels, types, required, maxLength, defaultValue, etc.) before rendering.

so-me templates:get <template-id>

Examples

# Full template definition
so-me templates:get 550e8400-e29b-41d4-a716-446655440000

# Just the field schema
so-me templates:get 550e8400-... | jq '.fields'

# Required fields only
so-me templates:get 550e8400-... | jq '.fields[] | select(.required) | .id'

templates:render

Render a template with your own field values. The output is an image uploaded to your media library; the response contains the imageUrl and the new fileId you can pass to posts:create.

so-me templates:render <template-id> [--data <json> | --file <path>]

Option	Description
`-d, --data <json-string>`	Inline JSON object mapping field IDs to values
`-f, --file <path>`	Path to a JSON file containing the field values

Exactly one of --data or --file is required. If neither is supplied the command exits with an error; the JSON must parse to an object whose keys are the template’s field ids.

Examples

# Inline values for a quote card
so-me templates:render 550e8400-... \
  --data '{"quote":"Ship early. Ship often.","author":"CLI test","bg":"#111","fg":"#fff"}'

# Values from a file
cat > values.json <<'EOF'
{
  "headline": "Now launching",
  "subheadline": "v2.0 in closed beta",
  "bg": "#5417d7"
}
EOF
so-me templates:render 550e8400-... --file values.json

# Render, then immediately schedule a post with the resulting image
RESULT=$(so-me templates:render 550e8400-... --data '{"quote":"..."}')
URL=$(echo "$RESULT" | jq -r '.imageUrl')
# Find the fileId that was added to your media library
FILE_ID=$(so-me media:search "$(basename $URL)" | jq -r '.data[0].id')
so-me posts:create -c "Quote of the day" --post-type IMAGE -m $FILE_ID --platform TWITTER

Required-field validation happens server-side. Call templates:get <id> first to see exactly which fields are required and their maxLength constraints — the render will 400 if any required field is missing.

Content templates are different from saved inbox replies (short text snippets for replying to DMs/comments). For those, use inbox:saved-replies / inbox:create-reply.They are also different from WhatsApp message templates (pre-approved outbound templates required by Meta for WhatsApp Business), documented at WhatsApp Templates.

Getting Started

Publishing

AI Studio

Inbox & Engagement

Analytics

Biolink

Team & Collaboration

Settings & Billing

Webhooks

Support

Available categories

templates:list

templates:get

templates:render

​Available categories

​templates:list

​templates:get

​templates:render

Available categories

templates:list

templates:get

templates:render