Documentation
Services
services.update_price
REST
ShippingPOST /api/v1/services/update_priceMCP tool
Liveservices.update_priceExposed on: REST API · Shop MCP server · Claude connector · Dash (in-app copilot) · Zapier. Part of the Services domain.
Operating contract
PERFORMS EXACTLY ONE KIND OF CHANGE PER CALL, selected by which parameter you provide: base_price for a flat, per-square-foot or per-hour service, or tiers for a tiered one. Sending the wrong one for the service's model is refused rather than guessed at.
THIS CHANGES A LIVE PRICE. It is what a customer is quoted on the booking page from the moment it saves, and there is no draft state and no approval step between this call and that page. Read the current price with services.get or services.tiers first and say what you are changing it from.
For a tiered service, ONLY the sizes you name are touched. The others keep the prices they had, which is what makes 'put the truck price up' safe to do on its own.
A by-quote (custom) service is refused: it has no set price to change, and the price for one is agreed on the quote itself.
Existing quotes, jobs and invoices are NOT re-priced. They snapshot what was agreed, which is the point — this changes what the NEXT customer is quoted.
IDEMPOTENCY IS none in the sense that matters: setting the same price twice is harmless, but there is no undo. The previous price is not kept anywhere a machine can read it back, so record it before you change it.
Who may call it
- Permission
shop.manageThe caller must hold shop.manage 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 |
|---|---|---|
| service_idrequired | stringuuid | The service to re-price, as returned by services.list or services.get. |
| base_price | number0–1000000 | The new price, for a flat / per_sqft / per_hour service. |
| tiers | object[] | New prices for a tiered service. Only the sizes named here change. |
| tiers[].vehicle_typerequired | string | — One of:car, truck, suv, van, coupe, motorcycle, commercial, exotic |
| tiers[].pricerequired | number0–1000000 | — |
Output
| Field | Type | Description |
|---|---|---|
| id | string | — |
| name | string | — |
| description | string | null | — |
| category | string | null | — |
| pricing_model | string | — |
| base_price | number | null | — |
| duration_minutes | number | null | — |
| cure_time_hours | number | null | — |
| active | boolean | — |
| bookable | boolean | — |
| addon | boolean | — |
| tax_exempt | boolean | — |
| sku | 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/services/update_price \
-H "Authorization: Bearer $SERVICEVIN_API_KEY" \
-H "Content-Type: application/json" \
-d '{"service_id":"9b2f1c6e-4a77-4d2b-9f31-0f1c9a8e5d20"}'const res = await fetch("https://www.servicevin.com/api/v1/services/update_price", {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.SERVICEVIN_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({
"service_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/services/update_price",
headers={"Authorization": f"Bearer {os.environ['SERVICEVIN_API_KEY']}"},
json={
"service_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": "services.update_price",
"arguments": {
"service_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 shop.manage. |
| 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. |