DevelopersChanges data

set_bookable_type_schedule

API reference — one of six tools an AI assistant can call on an Avrosh account.

What it does

Configure how one type is booked: kind ('day' per-night or 'time' appointment slots), slot length, service duration, turnaround buffer, minimum lead time, and weekly open hours. Hours use day keys mon..sun, each {open:'09:00', close:'18:00'}; a day absent from open_hours is CLOSED, and an empty open_hours means no slots are offered at all. Changing kind changes how availability is computed - confirm with the human first.

This is the exact text the model reads before deciding to call.

Parameters

business_idstringrequired

The id returned by list_businesses.

type_idstringrequired

From list_bookable_types.

kindstringoptional

one of: day · time

slot_minutesintegeroptional

Gap between offered start times, 5-1440.

duration_minutesintegeroptional

How long one booking takes, 5-1440.

buffer_minutesintegeroptional

Turnaround after each booking, 0-1440.

lead_minutesintegeroptional

Earliest a caller may book from now, minutes.

open_hoursobjectoptional

Weekly hours: { mon: {open:'09:00', close:'18:00'}, ... }. Absent day = closed.

Request

curl -X POST https://us.avrosh.com/mcp \
  -H "Authorization: Bearer $AVROSH_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"set_bookable_type_schedule","arguments":{"business_id":"926135ac-487d-4367-8bad-25397d0d4b87","type_id":"f81b…","slot_minutes":30,"duration_minutes":45,"open_hours":{"tue":{"open":"10:00","close":"19:00"},"sat":{"open":"09:00","close":"15:00"}}}}}'

Response

The result arrives as an MCP content block; the JSON below is what the text field parses to.

{
  "type": {
    "id": "f81b…",
    "granularity": "time",
    "slotMinutes": 30,
    "durationMinutes": 45
  }
}

Authentication

Every request carries Authorization: Bearer avk_…. Create a key in the Avrosh dashboard under Docs; it is shown once, because only its hash is stored.

One key reaches every business on the account that made it, and no others. There are no scopes to configure and nothing to switch on — a connected assistant receives the whole toolset. What bounds it is whose account the key belongs to, which is enforced in the database rather than by a permission anybody sets.

curl https://us.avrosh.com/mcp \
  -H "Authorization: Bearer $AVROSH_KEY"