Documentation
Comms
comms.block_texting
REST
ShippingPOST /api/v1/comms/block_textingMCP tool
Livecomms.block_textingExposed on: REST API · Shop MCP server · Claude connector · Dash (in-app copilot) · Zapier. Part of the Comms domain.
Operating contract
Sets the compliance flag every send rail on this platform already honours, so no text — automated, scheduled, campaign or typed by a rep — reaches this customer again. The composer disables, the agents skip them, comms.send_message refuses, and a queued send fails at its own re-check rather than going out.
THERE IS NO UNBLOCK HERE, AND THAT IS THE DESIGN. The same column carries two very different facts: a STOP the customer sent the carrier, and a block a member of staff applied. Nothing in the row says which, so a machine clearing it cannot tell whether it is undoing a colleague's decision or overriding a person who told the carrier to make it stop. The second of those is a regulatory violation, and the cost of being wrong is asymmetric enough that this capability only ever moves in the safe direction. Unblocking stays a person's decision at the inbox screen, where they can see the thread that led to it.
IT IS NOT THE MARKETING SWITCH. customers.set_marketing_consent governs campaigns; this governs every text of any kind. Blocking here does not clear marketing consent and clearing marketing consent does not block here.
Blocking somebody who is already blocked is a no-op and reports success, so a retrying integration cannot make anything worse.
Who may call it
- Permission
inbox.accessThe caller must hold Inbox at the ACT level. A read-only dashboard grant on the same section is refused.- Plan
- Every planNo plan gate. Available on every Service VIN plan.
- Retries
naturalNaturally idempotent — running it twice leaves the same world as running it once. A retrying integration needs no key.- Rate class
writeCounted against the write budget, which is tighter than a read.
Input
| Field | Type | Description |
|---|---|---|
| customer_idrequired | stringuuid | The customer to stop texting, as returned by customers.list or comms.resolve_contact. |
Output
| Field | Type | Description |
|---|---|---|
| id | string | — |
| texting_blocked | boolean | — |
Examples
Built from this capability's own schema — required fields and the ones carrying a default, and nothing invented. Paste one and it validates.
export SERVICEVIN_API_KEY=svk_live_…
curl -X POST https://www.servicevin.com/api/v1/comms/block_texting \
-H "Authorization: Bearer $SERVICEVIN_API_KEY" \
-H "Content-Type: application/json" \
-d '{"customer_id":"9b2f1c6e-4a77-4d2b-9f31-0f1c9a8e5d20"}'const res = await fetch("https://www.servicevin.com/api/v1/comms/block_texting", {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.SERVICEVIN_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({
"customer_id": "9b2f1c6e-4a77-4d2b-9f31-0f1c9a8e5d20"
}),
});
// Success and failure are both envelopes. Switch on error.code, never
// on error.message — the codes are stable, the messages are for people.
const payload = await res.json();
if (!res.ok) throw new Error(payload.error.code);
const data = payload.data;import os, requests
res = requests.post(
"https://www.servicevin.com/api/v1/comms/block_texting",
headers={"Authorization": f"Bearer {os.environ['SERVICEVIN_API_KEY']}"},
json={
"customer_id": "9b2f1c6e-4a77-4d2b-9f31-0f1c9a8e5d20"
},
timeout=30,
)
payload = res.json()
if not res.ok:
raise RuntimeError(payload["error"]["code"])
data = payload["data"]{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "comms.block_texting",
"arguments": {
"customer_id": "9b2f1c6e-4a77-4d2b-9f31-0f1c9a8e5d20"
}
}
}Refusals
The four gates run in this order on every surface, and the order is not arbitrary — see Authentication.
| Status | Code | When |
|---|---|---|
| 404 | not_found | The id is unknown, or the feature is not enabled for this account. Deliberately the same answer for both. |
| 403 | forbidden | This login does not hold inbox.access. |
| 403 | insufficient_scope | The credential is read-only and this capability writes. |
| 422 | validation_error | An argument was wrong. The message names the field. |
| 429 | rate_limited | Too many write calls. Back off and retry. |
| 500 | internal_error | Something failed on our side. Nothing was changed. |