Documentation
Booking
booking.approval_queue
REST
ShippingPOST /api/v1/booking/approval_queueMCP tool
Livebooking.approval_queueExposed on: REST API · Shop MCP server · Claude connector · Dash (in-app copilot) · Zapier. Part of the Booking domain.
Operating contract
How much unanswered work is sitting in the shop's booking queue. Under approval mode a customer's slot is HELD but nothing is confirmed until somebody decides — so a queue nobody is watching is a set of customers who were told the shop would come back to them and never were.
oldest_pending_at IS THE NUMBER THAT MATTERS, not the count. A queue of one that has been sitting for three days is a worse failure than a queue of nine placed this morning.
needs_review is a different thing from pending: those bookings were taken, but something about them wants a human's eye before the shop commits the bay.
NOTHING EXPIRES. No sweep auto-declines an old request, deliberately — how long a shop may sit on a booking is a commercial decision the owner has not made, and inventing one would cancel real work on real calendars. A request only leaves this queue when somebody answers it.
A shop that has never touched its approval setting provably has no queue and reads as zero without a query. Deciding — accepting or declining — is not a capability: it is the shop's judgement about whether it wants the work.
THIS IS THE STAFF SIDE OF THE DOMAIN and is gated accordingly. booking.get is how a customer's own assistant reads one appointment back, with their manage token as the credential.
This is a set of counts, entirely returned, 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 |
|---|---|---|
| pending | number | — |
| needs_review | number | — |
| oldest_pending_at | 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/approval_queue \
-H "Authorization: Bearer $SERVICEVIN_API_KEY" \
-H "Content-Type: application/json" \
-d '{}'const res = await fetch("https://www.servicevin.com/api/v1/booking/approval_queue", {
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/approval_queue",
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.approval_queue",
"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. |