create_bookable_type
API reference — one of six tools an AI assistant can call on an Avrosh account.
What it does
Add one bookable type. Only write what the human told you - name and price come from them. kind: 'day' for per-night/per-day (hotel room, rental car), 'time' for appointment slots (haircut, treatment); omit it and the business's own default applies. price is the base rate, price_max the top of the range when rates vary; both whole numbers in the business's own currency. A same-name twin is refused with the existing id. Appointment hours and slot lengths are set afterwards with set_bookable_type_schedule. Photos are dashboard-only.
This is the exact text the model reads before deciding to call.
Parameters
business_idstringrequired
The id returned by list_businesses.
namestringrequired
The type name as customers know it. Max 160 chars.
priceintegeroptional
Base rate, whole number in the business's own currency.
price_maxintegeroptional
Top of the rate range when it varies by date.
sleepsintegeroptional
Maximum people it fits. Omit when unknown - never guess.
descriptionstringoptional
What it is, as read to customers. Max 2000 chars.
bed_configstringoptional
E.g. '1 king' or '2 twin'. Rooms only.
viewstringoptional
E.g. 'garden', 'sea'. Max 120 chars.
amenitiesarrayoptional
Free-form tags. Max 40.
kindstringoptional
'day' = per-night, 'time' = appointment slots.
one of: day · time
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":"create_bookable_type","arguments":{"business_id":"926135ac-487d-4367-8bad-25397d0d4b87","name":"Haircut - classic","price":75000,"kind":"time"}}}'Response
The result arrives as an MCP content block; the JSON below is what the text field parses to.
{
"type": {
"id": "f81b…",
"name": "Haircut - classic",
"granularity": "time"
}
}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"All tools
list_businesses · get_business · list_calls · get_transcript · create_business · update_business · list_knowledge · add_knowledge_chapter · update_knowledge_chapter · delete_knowledge_chapter · restore_knowledge_chapter · list_menu_items · create_menu_item · update_menu_item · set_menu_item_availability · delete_menu_item · restore_menu_item · remove_menu_item_photo · set_menu_item_thumbnail · list_bookable_types · create_bookable_type · update_bookable_type · set_bookable_type_schedule · delete_bookable_type · restore_bookable_type · list_bookings · get_booking · confirm_booking · cancel_booking · list_work_queue · accept_order · finish_order · accept_request · finish_request · assign_request · list_customers · get_customer · export_customer_data · erase_customer