Contents

API reference / Actions

Propose sending the brief, a report, a rival card or chosen posts to Slack or email

POST /api/v1/actions/send

propose_send Write MCP tool

Builds the message now, from stored data, and puts it in the approval queue; it is sent only when a person approves it in the app. what: brief (the playbook's ready list with its quotes, links, reasons and the drafts already written; for founders' answer list, developer relations' unanswered threads), insights (the product marketers' weekly digest with why customers leave each rival), report (a client's white-label report; needs project), rival_card (one rival; needs competitor) or mentions (posts you choose; needs mention_ids). channel and target say where: email an address, slack a channel ID or an incoming-webhook address, discord or teams a webhook address.

A full-access key (ss_sk_…), or an editor or owner signed in.

Request body

JSON, sent with Content-Type: application/json.

NameTypeDescription
what required string
One of: brief insights report rival_card mentions
channel required string
One of: email slack discord teams
target required string
up to 500 characters
Where it goes: an address, a Slack channel ID or webhook address, a Discord or Teams webhook address.
project string The client or brand (a report needs it; a brief and the insights use it to narrow to one client).
playbook string A playbook id to build a brief from, instead of the workspace's.
competitor string A rival's name or id (rival_card).
days integer
1–90
mention_ids array of string
up to 12 items
The posts to send (mentions), up to 12.
note string
up to 400 characters
A line to add to the message.
title string
up to 120 characters
A title for a mentions message.

Returns

{ data: Action, approval }

Example

curl -X POST "https://sniffington.com/api/v1/actions/send" \
  -H "Authorization: Bearer $SCOUT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"what":"brief","channel":"email","target":"…"}'