Documentation
Services
services.price_book
REST
ShippingPOST /api/v1/services/price_bookMCP tool
Liveservices.price_bookExposed on: REST API · Shop MCP server · Claude connector · Dash (in-app copilot) · Zapier. Part of the Services domain.
Operating contract
THE WHOLE PRICE BOOK IN ONE READ — every live service, its category, its description, its duration and every price it has, including the per-vehicle-size tiers, with no paging.
This exists because the alternative is expensive and error-prone: services.list plus a services.tiers call per service is dozens of round trips to answer 'what do you charge', and a model that gets bored halfway through answers about half a menu.
Use it for anything that needs the shop's pricing as a whole — an audit, a comparison, a summary for the owner. Use services.get when you only care about one.
Inactive and retired services are left off, so anything missing is something the shop stopped selling. Cost and margin are NOT here: this is the price book, and services.tiers is where the shop's own economics live.
It reads the same shaping quotes.catalog uses, so the prices here and the prices a quote is built from cannot disagree.
No paging and no cap — every live service comes back, so nothing is truncated.
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
readCounted against the read budget — the widest of the four.
Input
This capability takes no arguments.
Output
| Field | Type | Description |
|---|---|---|
| currency | string | — |
| items | object[] | — |
| items[].id | string | — |
| items[].name | string | — |
| items[].category | string | null | — |
| items[].description | string | null | — |
| items[].base_price | number | null | — |
| items[].duration_minutes | number | null | — |
| items[].tiers | object[] | — |
| items[].tiers[].vehicle_type | string | — |
| items[].tiers[].price | number | — |
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/price_book \
-H "Authorization: Bearer $SERVICEVIN_API_KEY" \
-H "Content-Type: application/json" \
-d '{}'const res = await fetch("https://www.servicevin.com/api/v1/services/price_book", {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.SERVICEVIN_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({}),
});
// 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/price_book",
headers={"Authorization": f"Bearer {os.environ['SERVICEVIN_API_KEY']}"},
json={},
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.price_book",
"arguments": {}
}
}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. |
| 422 | validation_error | An argument was wrong. The message names the field. |
| 429 | rate_limited | Too many read calls. Back off and retry. |
| 500 | internal_error | Something failed on our side. Nothing was changed. |