Email signatures

Create an email signature and render it. Nothing is sent — but the FIRST signature in a scope automatically becomes that scope's default, so an account signature created here starts appending to outbound email from the next send. Image URLs (logo, portrait, banner) must be publicly reachable: mail clients fetch them directly and a login-protected URL shows as a broken image in every inbox.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/email_signatures.create \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Example"
  }'

Over MCP the same operation is the tool email_signatures_create at https://app.chirply.io/api/mcp, same bearer token, same input.

Permanently delete a signature. This cannot be undone. Email already sent keeps the signature it went out with; new email stops using this one, and if it was a default the oldest remaining signature in that scope takes over.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/email_signatures.delete \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool email_signatures_delete at https://app.chirply.io/api/mcp, same bearer token, same input.

Fetch one signature by id, with its fields and the exact HTML and plain text it appends to an email.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/email_signatures.get \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool email_signatures_get at https://app.chirply.io/api/mcp, same bearer token, same input.

List every email signature in the account — shared ones and each teammate's own — with the rendered HTML each would append. Reads only.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/email_signatures.list \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "scope": "personal"
  }'

Over MCP the same operation is the tool email_signatures_list at https://app.chirply.io/api/mcp, same bearer token, same input.

Render signature HTML and plain text from a set of fields WITHOUT saving anything. Use it to check a layout before creating a signature, or to produce markup to paste into Gmail, Outlook or Apple Mail. Changes nothing and sends nothing.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/email_signatures.preview \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "template": "showcase",
    "full_name": "Example"
  }'

Over MCP the same operation is the tool email_signatures_preview at https://app.chirply.io/api/mcp, same bearer token, same input.

Turn automatic signature signing on or off for the CALLING USER — the same switch as “Sign my email automatically” in the signature designer. On, their signature is appended to one-to-one email they send from the inbox; off, their email goes out unsigned unless a message opts in. Affects only this user's own future sends and changes what those recipients see; it sends nothing itself, and other teammates' settings and the signatures themselves are untouched.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/email_signatures.set_auto_append \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "enabled": true
  }'

Over MCP the same operation is the tool email_signatures_set_auto_append at https://app.chirply.io/api/mcp, same bearer token, same input.

Make one signature the default within its own scope, demoting the current default there. An account default is what signs email from anyone who has not made their own, so this changes what recipients see on the next send.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/email_signatures.set_default \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool email_signatures_set_default at https://app.chirply.io/api/mcp, same bearer token, same input.

Update an existing signature and re-render it. Omitted fields are left alone, except socials, which replaces the whole list when supplied. Sends nothing — but this signature is appended to email from the next send onwards, so a change here changes what recipients see.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/email_signatures.update \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool email_signatures_update at https://app.chirply.io/api/mcp, same bearer token, same input.