Endpoint
Set speaker reply status
POST/api/public/v1/speakers/{speaker_id}/reply-statuswrite
Update reply status for a speaker. Allowed: replied, booked, no_reply, or null to clear.
Request
curl -X POST "https://sayintel.com/api/public/v1/speakers/<speaker_id>/reply-status" \
-H "Authorization: Bearer $SAYINTEL_TOKEN" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: $(uuidgen)" \
-d '{"reply_status": "<reply_status>"}'Try it out
Try it outPOST/api/public/v1/speakers/{speaker_id}/reply-statuswrite
Sent as a bearer token to this site only, and kept in this tab's session storage. It is never written to disk or sent anywhere else.
Paste an API key to run.
Path parameters
| Name | In | Type | Required | Description |
|---|---|---|---|---|
| speaker_id | path | string | yes | — |
Body
| Name | In | Type | Required | Description |
|---|---|---|---|---|
| reply_status | body | stringreplied | booked | no_reply | yes | — |
Response
{
"ok": true,
"tool": "set_speaker_reply_status",
"kind": "write",
"data": { ... },
"error": null
}Notes
- Scope required: write. How scopes work.
- Accepts Idempotency-Key. A retry with the same key replays the first result instead of repeating the work.
- Same capability over MCP as the tool set_speaker_reply_status. MCP setup.