replies

replies.draft

Write a reply draft into a lead's Sales Inbox thread. A person reviews and sends it in the app, this can send nothing.

Dispatched to replies.draft on POST /mcp/mutate. This route is a different URL for the same call: the request is answered by the same dispatcher, with the same authentication, the same scope check, the same organisation scoping and the same refusals.

  • Scope: write
  • A free sandbox key may call it
  • MCP tools that wrap the same function: selda_draft_reply
  • Filled in from your API key, never sent by you: orgId
post/v1/replies/draft

Request

  • Base URL: https://api.selda.ai
  • URL: https://api.selda.ai/v1/replies/draft
  • Auth: HTTP bearer

Request body

leadIdstring required
bodystring required
instructionstring

What the person asked for in their own words ("tee tästä lyhyempi"). Optional, kept only in the draft history beside the text, it changes nothing about what is stored in the composer. The selda_draft_reply tool schemas in api/mcp.ts and mcp-server/index.ts do not pass it yet, so this arrives empty on the tool path until they do.

Response

The call succeeded.

valueunknown required
request_idstring required

Echoed in the X-Request-Id header.

Changes

No recorded changes to this operation across all 1 revision of this API.