Documentation
Booking
booking.services
REST
ShippingPOST /api/v1/booking/servicesMCP tool
Livebooking.servicesExposed on: REST API · Booking MCP server. Part of the Booking domain.
Operating contract
The shop's public booking menu: every service the storefront offers, its category, how long it takes, and what it costs — as a flat base_price or as per-vehicle-size tiers.
A TIERED SERVICE HAS NO SINGLE PRICE. Pick the tier matching the customer's vehicle, and if you do not know what they drive, ASK. Quoting the cheapest tier because it was first is how a van customer is charged the sedan price.
A service whose tiers has no entry for the customer's vehicle type is one this shop has not priced for that size. Do not guess a number: say the shop will confirm the price, and book it only if booking.deposit_policy reports it as bookable.
Each id is what booking.availability, booking.hold, booking.book and booking.deposit_policy all take in service_ids.
vehicle_types is the closed set of size labels this shop's tiers are keyed on — use one of those exact strings, never a make or a model.
Returns the whole menu; there is nothing to page through.
Who may call it
- Permission
- NoneThe public booking menu. It is served to anonymous visitors at /book/<slug> already, so gating the same rows behind a staff permission would protect nothing and would stop a voice agent quoting the shop's own advertised price.
- 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 | — |
| online_booking | boolean | — |
| vehicle_types | string[] | — |
| items | object[] | — |
| items[].id | string | — |
| items[].name | string | — |
| items[].category | string | — |
| items[].description | string | null | — |
| items[].duration_minutes | number | null | — |
| items[].base_price | 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/booking/services \
-H "Authorization: Bearer $SERVICEVIN_API_KEY" \
-H "Content-Type: application/json" \
-d '{}'const res = await fetch("https://www.servicevin.com/api/v1/booking/services", {
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/booking/services",
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": "booking.services",
"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. |
| 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. |