Documentation
Shop
shop.business_hours
REST
ShippingPOST /api/v1/shop/business_hoursMCP tool
Liveshop.business_hoursExposed on: REST API · Shop MCP server · Claude connector · Dash (in-app copilot) · Zapier. Part of the Shop domain.
Operating contract
The shop's working week: which weekdays it opens, and the hours it works on each. null for a day means CLOSED — not 'unset' and not 'all day'.
THESE HOURS BOUND EVERYTHING ON THE CALENDAR. The public booking grid, the capacity caps, the scheduling agent and the day board all measure against them, so a question about availability that ignores them will be wrong on exactly the days it matters.
Hours are LOCAL WALL CLOCK in the shop's own timezone, open inclusive and close exclusive: 8 to 17 means the last work starts before five, not at five.
configured: false means this shop has never set its hours, and everything downstream is running on the product's default week (weekdays and Saturday, eight to five). Say so rather than quoting the defaults as the shop's own decision.
This is one week of settings, 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 |
|---|---|---|
| configured | boolean | — |
| timezone | string | — |
| days | object[] | — |
| days[].weekday | string | — |
| days[].open | number | null | — |
| days[].close | number | null | — |
| days[].closed | boolean | — |
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/shop/business_hours \
-H "Authorization: Bearer $SERVICEVIN_API_KEY" \
-H "Content-Type: application/json" \
-d '{}'const res = await fetch("https://www.servicevin.com/api/v1/shop/business_hours", {
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/shop/business_hours",
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": "shop.business_hours",
"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. |