Documentation
Booking
booking.reschedule
REST
ShippingPOST /api/v1/booking/rescheduleMCP tool
Livebooking.rescheduleExposed on: REST API · Booking MCP server. Part of the Booking domain.
Operating contract
Moves the appointment the manage_token names to start, re-validating that time through the same engine that drew the grid and refusing rather than double-booking the shop.
GET THE NEW TIME FROM booking.get. Its availability grid is narrowed to this exact booking — the same services, the same car, the same installer — so a time from it is a time this appointment can actually move to. A time from a fresh booking.availability call may not be.
moved: false with reason: locked means it is inside the shop's cut-off or already under way (give them the shop's number); slot_taken means somebody took that time while you were talking (offer another); invalid means start was not a real instant; unavailable means the booking could not be read at all.
Rescheduling does not ask the customer to verify anything. Cancelling does — see booking.cancel.
Who may call it
- Permission
- NoneThe customer moving their own appointment with their own manage token — byte for byte the write the manage page makes with no login. Staff move a job with `jobs.schedule`, which IS section-gated.
- 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 |
|---|---|---|
| manage_tokenrequired | stringmax 512 chars, min 8 chars | The token from the booking's manage_url, as returned by booking.book. |
| startrequired | string | The new slot's `start`, copied from the grid on booking.get. An ISO 8601 instant. |
Output
| Field | Type | Description |
|---|---|---|
| moved | boolean | — |
| scheduled_start | string | null | — |
| scheduled_end | string | null | — |
| reason | 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/booking/reschedule \
-H "Authorization: Bearer $SERVICEVIN_API_KEY" \
-H "Content-Type: application/json" \
-d '{"manage_token":"…","start":"…"}'const res = await fetch("https://www.servicevin.com/api/v1/booking/reschedule", {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.SERVICEVIN_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({
"manage_token": "…",
"start": "…"
}),
});
// 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/reschedule",
headers={"Authorization": f"Bearer {os.environ['SERVICEVIN_API_KEY']}"},
json={
"manage_token": "…",
"start": "…"
},
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.reschedule",
"arguments": {
"manage_token": "…",
"start": "…"
}
}
}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 | 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. |