Documentation
Comms
comms.set_contact_language
REST
ShippingPOST /api/v1/comms/set_contact_languageMCP tool
Livecomms.set_contact_languageExposed on: REST API · Shop MCP server · Claude connector · Dash (in-app copilot) · Zapier. Part of the Comms domain.
Operating contract
Records the language a customer reads in, which the inbox's translation uses when it shows staff an incoming message and when it renders a draft going out.
IT DOES NOT TRANSLATE ANYTHING BY ITSELF and it does not change what has already been sent. It is a preference on the customer record, read at the moment a message is displayed or drafted.
Pass a two-letter code (es, fr, pa, zh). Pass null — or en — to clear the preference and go back to no translation; clearing removes only the language keys and leaves any importer's other identifiers on the record untouched.
SET IT FROM EVIDENCE, NOT FROM A NAME. The right trigger is a customer who has actually written to the shop in that language, or who said so. Inferring a language from somebody's name is how a shop starts sending Spanish to a customer who has read English their whole life.
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 set, as returned by customers.list or comms.resolve_contact. |
| languagerequired | string | null | A two-letter language code, or null to clear the preference. |
Output
| Field | Type | Description |
|---|---|---|
| id | string | — |
| language | string | null | — |
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/set_contact_language \
-H "Authorization: Bearer $SERVICEVIN_API_KEY" \
-H "Content-Type: application/json" \
-d '{"customer_id":"9b2f1c6e-4a77-4d2b-9f31-0f1c9a8e5d20","language":"…"}'const res = await fetch("https://www.servicevin.com/api/v1/comms/set_contact_language", {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.SERVICEVIN_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({
"customer_id": "9b2f1c6e-4a77-4d2b-9f31-0f1c9a8e5d20",
"language": "…"
}),
});
// 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/set_contact_language",
headers={"Authorization": f"Bearer {os.environ['SERVICEVIN_API_KEY']}"},
json={
"customer_id": "9b2f1c6e-4a77-4d2b-9f31-0f1c9a8e5d20",
"language": "…"
},
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.set_contact_language",
"arguments": {
"customer_id": "9b2f1c6e-4a77-4d2b-9f31-0f1c9a8e5d20",
"language": "…"
}
}
}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. |