Documentation
Leads
leads.update
REST
ShippingPOST /api/v1/leads/updateMCP tool
Liveleads.updateExposed on: REST API · Shop MCP server · Claude connector · Dash (in-app copilot) · Zapier. Part of the Leads domain.
Operating contract
PERFORMS EXACTLY ONE CHANGE PER CALL, selected by which parameter you provide: first_name, last_name, company_name, phone, email, vehicle_description, source, estimated_value, follow_up_on or clear_follow_up. To make several changes, call this once per change.
Sending two at once is refused rather than guessed at, so a mistyped field never silently overwrites something nobody meant to touch.
follow_up_on and clear_follow_up are separate parameters on purpose — 'chase them on Tuesday' and 'stop chasing them' are different decisions, and a nullable date field makes the second one look like a typo.
STATUS AND OWNER ARE NOT HERE. leads.set_status and leads.assign are their own capabilities because their consequences are different: a status move can fire the shop's automations, and an assignment rings a teammate. That split is the whole reason a mis-set field here cannot text a customer.
Returns the lead as it now stands.
Who may call it
- Permission
leads.accessThe caller must hold Leads 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 |
|---|---|---|
| lead_idrequired | stringuuid | The lead to change, as returned by leads.list or leads.get. |
| first_name | stringmax 120 chars | A new first name. |
| last_name | stringmax 120 chars | A new last name. |
| company_name | stringmax 200 chars | A new company name. |
| phone | stringmax 40 chars | A new phone number, any format. |
| stringmax 200 chars | A new email address. | |
| vehicle_description | stringmax 300 chars | A new description of the car, in the customer's words. |
| source | stringmax 60 chars | A corrected source key, as returned by leads.sources. |
| estimated_value | number0–10000000 | What the job is worth if it lands, in the shop's currency. |
| follow_up_on | string | The date to chase them on, YYYY-MM-DD in the shop's own calendar. |
| clear_follow_up | boolean | True removes the follow-up reminder entirely. |
Output
| Field | Type | Description |
|---|---|---|
| id | string | — |
| name | string | — |
| string | null | — | |
| phone | string | null | — |
| source | string | null | — |
| status | string | — |
| assigned_to | string | null | — |
| next_followup_at | string | null | — |
| created_at | string | — |
| company_name | string | null | — |
| vehicle_description | string | null | — |
| service_interest | string[] | — |
| tags | string[] | — |
| estimated_value | number | null | — |
| lost_reason | string | null | — |
| last_contacted_at | string | null | — |
| customer_id | string | null | — |
| stage | string | null | — |
| score | number | null | — |
| updated_at | string | — |
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/leads/update \
-H "Authorization: Bearer $SERVICEVIN_API_KEY" \
-H "Content-Type: application/json" \
-d '{"lead_id":"9b2f1c6e-4a77-4d2b-9f31-0f1c9a8e5d20"}'const res = await fetch("https://www.servicevin.com/api/v1/leads/update", {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.SERVICEVIN_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({
"lead_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/leads/update",
headers={"Authorization": f"Bearer {os.environ['SERVICEVIN_API_KEY']}"},
json={
"lead_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": "leads.update",
"arguments": {
"lead_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 leads.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. |