Draft a reply
POST /api/v1/mentions/{mention}/draft
Writes a short, help-first reply in the post's own register and saves it as the draft, in the voice of the connected account that would answer it (the brand's, or a person's on the team; see get_reply_route), or of `connection_id`. The response carries `why_this_post`: the fixed sentences that say why this post is on your list (what the author is doing, how strong a match, who it is about, how old, whether anyone answered, and whether it is ready under your playbook). Honest voice, the disclosure line where a person's account names the brand, no link unless asked. Nothing is posted; post_reply sends it once you've approved it.
A full-access key (ss_sk_…), or an editor or owner signed in.
Parameters
| Name | Type | Description |
|---|---|---|
mention requiredpath |
string | The mention's id. |
Request body
JSON, sent with Content-Type: application/json.
| Name | Type | Description |
|---|---|---|
connection_id |
integer or null | Draft as this connected account instead of the one routing picks. |
as_auto_reply |
boolean | Dry run of what auto-reply would do with this post: the drafter may decline and a critic reviews the draft. Returns `skipped` with the reason (and an empty draft) when auto-reply would stay quiet. Nothing is saved. In a project with conquest mode on, also returns `angle` (the attack point or fact used) and `move`. |
conquest |
boolean | A plain draft follows the project's conquest mode when it is on (set false to turn that off for this draft). |
Example
curl -X POST "https://sniffington.com/api/v1/mentions/{mention}/draft" \
-H "Authorization: Bearer $SCOUT_API_KEY" \
-H "Content-Type: application/json" \
-d '{"connection_id":1,"as_auto_reply":true}'