Booking setup

List booking event types

crm.booking.event_types.list

Lists the meeting types sellers publish on their public booking pages (title, slug, duration, buffers, notice, location, custom questions, reminders, enabled), oldest first and paginated by cursor (limit 50 by default, up to 200), each with the seller's name (user_name). Filter by vendor_user_id for one seller. The order a seller set for their page is the order field. Read-only.

Scope

crm:read

Permission

View the module

MCP tool

crm_booking_event_types_listOn the full surface; on the compact one, mb_execute_operation with id: "crm.booking.event_types.list".

Declared cost: up to 202 reads and 0 writes per call (they count against the daily quota).

Parameters

Response

Errors

Example

curl "https://api.mb-suite.com/v1/crm/booking/event-types" \
  -H "Authorization: Bearer $MB_API_KEY"

Try it with your test API key

With a test API key the request always goes to your practice organization: example data you can reset.

curl "https://api.mb-suite.com/v1/crm/booking/event-types" \
  -H "Authorization: Bearer $MB_TEST_KEY"

Create a booking event type

crm.booking.event_types.create

Creates a meeting type for a seller's public booking page (user_id: a member of the CRM team): title, slug (unique per seller), duration, buffers, minimum notice, booking horizon, daily cap, slot step, location (meet, zoom, phone, in_person, custom_url), custom questions, phone field, email and WhatsApp reminders, blocked dates and redirect. It is created disabled: enable it with crm.booking.event_types.set_enabled. A WhatsApp reminder needs the phone field enabled and required. Own: manage_own_booking; another seller's: manage_any_booking.

Scope

crm:write

Permission

Edit in the module

MCP tool

crm_booking_event_types_createOn the full surface; on the compact one, mb_execute_operation with id: "crm.booking.event_types.create".

Declared cost: up to 2 reads and 1 writes per call (they count against the daily quota).

Parameters

Response

Errors

Example

curl -X POST "https://api.mb-suite.com/v1/crm/booking/event-types" \
  -H "Authorization: Bearer $MB_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "user_id": "USER_ID",
  "slug": "SLUG",
  "title": "TITLE",
  "location": {}
}'

Try it with your test API key

With a test API key the request always goes to your practice organization: example data you can reset.

curl -X POST "https://api.mb-suite.com/v1/crm/booking/event-types" \
  -H "Authorization: Bearer $MB_TEST_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "user_id": "USER_ID",
  "slug": "SLUG",
  "title": "TITLE",
  "location": {}
}'

Update a booking event type

crm.booking.event_types.update

Updates any field of an event type (the same ones as on create); only the fields sent change, and a changed slug must stay unique for the seller. The WhatsApp reminder rule is checked against the merged result. To enable or disable it use crm.booking.event_types.set_enabled. Own: manage_own_booking; another seller's: manage_any_booking.

Scope

crm:write

Permission

Edit in the module

MCP tool

crm_booking_event_types_updateOn the full surface; on the compact one, mb_execute_operation with id: "crm.booking.event_types.update".

Declared cost: up to 2 reads and 1 writes per call (they count against the daily quota).

Parameters

Response

Errors

Example

curl -X PATCH "https://api.mb-suite.com/v1/crm/booking/event-types/{event_type_id}" \
  -H "Authorization: Bearer $MB_API_KEY"

Try it with your test API key

With a test API key the request always goes to your practice organization: example data you can reset.

curl -X PATCH "https://api.mb-suite.com/v1/crm/booking/event-types/{event_type_id}" \
  -H "Authorization: Bearer $MB_TEST_KEY"

Enable or disable a booking event type

crm.booking.event_types.set_enabled

Turns an event type on (it shows on the seller's public booking page and takes bookings) or off (hidden, configuration kept; existing bookings are not touched). Idempotent. Own: manage_own_booking; another seller's: manage_any_booking.

Scope

crm:write

Permission

Edit in the module

MCP tool

crm_booking_event_types_set_enabledOn the full surface; on the compact one, mb_execute_operation with id: "crm.booking.event_types.set_enabled".

Declared cost: up to 1 reads and 1 writes per call (they count against the daily quota).

Parameters

Response

Errors

Example

curl -X POST "https://api.mb-suite.com/v1/crm/booking/event-types/{event_type_id}/enabled" \
  -H "Authorization: Bearer $MB_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "enabled": true
}'

Try it with your test API key

With a test API key the request always goes to your practice organization: example data you can reset.

curl -X POST "https://api.mb-suite.com/v1/crm/booking/event-types/{event_type_id}/enabled" \
  -H "Authorization: Bearer $MB_TEST_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "enabled": true
}'

Duplicate a booking event type

crm.booking.event_types.duplicate

Copies an event type for the same seller with a free slug ('-copia', '-copia-2'…), the title plus ' (copia)', the counters at zero and disabled. Returns the new id. Own: manage_own_booking; another seller's: manage_any_booking.

Scope

crm:write

Permission

Edit in the module

MCP tool

crm_booking_event_types_duplicateOn the full surface; on the compact one, mb_execute_operation with id: "crm.booking.event_types.duplicate".

Declared cost: up to 52 reads and 1 writes per call (they count against the daily quota).

Parameters

Response

Errors

Example

curl -X POST "https://api.mb-suite.com/v1/crm/booking/event-types/{event_type_id}/duplicate" \
  -H "Authorization: Bearer $MB_API_KEY"

Try it with your test API key

With a test API key the request always goes to your practice organization: example data you can reset.

curl -X POST "https://api.mb-suite.com/v1/crm/booking/event-types/{event_type_id}/duplicate" \
  -H "Authorization: Bearer $MB_TEST_KEY"

Delete a booking event type

crm.booking.event_types.delete

Deletes an event type for good (it does not go to the trash). Refused with event_type_has_upcoming_bookings while it has confirmed bookings ahead: disable it with crm.booking.event_types.set_enabled instead. Past bookings keep their data. The booking lead sources bound to it are paused (they would take no more leads); the dry run names them. Own: manage_own_booking; another seller's: manage_any_booking.

Needs confirmation: first dry_run: true (preview and confirm_token, valid 10 minutes and for one run), then the same body with confirm_token. In a few operations only with certain data: the description says when. Why and how: Dry run and confirm_token.

Scope

crm:write and “Allow deletions” (crm:delete in OAuth)

Permission

Edit in the module

MCP tool

crm_booking_event_types_deleteOn the full surface; on the compact one, mb_execute_operation with id: "crm.booking.event_types.delete".

Declared cost: up to 102 reads and 21 writes per call (they count against the daily quota).

Parameters

Response

Errors

Example

curl -X POST "https://api.mb-suite.com/v1/crm/booking/event-types/{event_type_id}/delete" \
  -H "Authorization: Bearer $MB_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "dry_run": true
}'

Try it with your test API key

With a test API key the request always goes to your practice organization: example data you can reset.

curl -X POST "https://api.mb-suite.com/v1/crm/booking/event-types/{event_type_id}/delete" \
  -H "Authorization: Bearer $MB_TEST_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "dry_run": true
}'

Reorder a seller's booking event types

crm.booking.event_types.reorder

Sets the order of a seller's event types on their booking page and list: ordered_ids (up to 200) become order 0, 1, 2… Every id must be an event type of that seller (user_id). Idempotent. Own: manage_own_booking; another seller's: manage_any_booking.

Scope

crm:write

Permission

Edit in the module

MCP tool

crm_booking_event_types_reorderOn the full surface; on the compact one, mb_execute_operation with id: "crm.booking.event_types.reorder".

Declared cost: up to 200 reads and 200 writes per call (they count against the daily quota).

Parameters

Response

Errors

Example

curl -X POST "https://api.mb-suite.com/v1/crm/booking/event-types/reorder" \
  -H "Authorization: Bearer $MB_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "user_id": "USER_ID",
  "ordered_ids": [
    "ORDERED_ID"
  ]
}'

Try it with your test API key

With a test API key the request always goes to your practice organization: example data you can reset.

curl -X POST "https://api.mb-suite.com/v1/crm/booking/event-types/reorder" \
  -H "Authorization: Bearer $MB_TEST_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "user_id": "USER_ID",
  "ordered_ids": [
    "ORDERED_ID"
  ]
}'

Set a seller's weekly availability

crm.booking.schedules.update

Replaces a seller's weekly booking availability: an IANA time zone and seven days (mon…sun), each with up to six ranges in minutes from midnight (end after start; an empty day is unavailable). Event types without their own schedule offer slots from it. The seller must be on the CRM team. Own: manage_own_booking; another seller's: manage_any_booking.

Scope

crm:write

Permission

Edit in the module

MCP tool

crm_booking_schedules_updateOn the full surface; on the compact one, mb_execute_operation with id: "crm.booking.schedules.update".

Declared cost: up to 2 reads and 1 writes per call (they count against the daily quota).

Parameters

Response

Errors

Example

curl -X PATCH "https://api.mb-suite.com/v1/crm/booking/schedules/{user_id}" \
  -H "Authorization: Bearer $MB_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "schedule": {}
}'

Try it with your test API key

With a test API key the request always goes to your practice organization: example data you can reset.

curl -X PATCH "https://api.mb-suite.com/v1/crm/booking/schedules/{user_id}" \
  -H "Authorization: Bearer $MB_TEST_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "schedule": {}
}'

List which sellers take bookings

crm.booking.settings.list

Lists every seller of the CRM team with their name (display_name, as the team shows it) and whether their public booking is on (booking_enabled). Use crm.booking.settings.get for one seller's full page and schedule. Read-only.

Scope

crm:read

Permission

View the module

MCP tool

crm_booking_settings_listOn the full surface; on the compact one, mb_execute_operation with id: "crm.booking.settings.list".

Declared cost: up to 400 reads and 0 writes per call (they count against the daily quota).

Parameters

No parameters.

Response

Errors

Example

curl "https://api.mb-suite.com/v1/crm/booking/settings" \
  -H "Authorization: Bearer $MB_API_KEY"

Try it with your test API key

With a test API key the request always goes to your practice organization: example data you can reset.

curl "https://api.mb-suite.com/v1/crm/booking/settings" \
  -H "Authorization: Bearer $MB_TEST_KEY"

Get a seller's booking page and schedule

crm.booking.settings.get

Returns a seller's booking settings: whether booking is on, the weekly schedule and time zone, the public slug, bio, display name, avatar, default page language, calendar color and calendar sharing; null if they never configured them. Own: view_own_bookings; another seller's: view_any_booking.

Scope

crm:read

Permission

View the module

MCP tool

crm_booking_settings_getOn the full surface; on the compact one, mb_execute_operation with id: "crm.booking.settings.get".

Declared cost: up to 1 reads and 0 writes per call (they count against the daily quota).

Parameters

Response

Errors

Example

curl "https://api.mb-suite.com/v1/crm/booking/settings/{user_id}" \
  -H "Authorization: Bearer $MB_API_KEY"

Try it with your test API key

With a test API key the request always goes to your practice organization: example data you can reset.

curl "https://api.mb-suite.com/v1/crm/booking/settings/{user_id}" \
  -H "Authorization: Bearer $MB_TEST_KEY"

Update a seller's booking page

crm.booking.settings.update

Updates a seller's public booking page: bio, display name, default language (es, en, pt-BR) and avatar (a public https URL or an MB Suite storage path; null removes it). Fields left out keep their value. The slug changes with crm.booking.settings.set_slug and the switch with crm.booking.settings.set_enabled. Own: manage_own_booking; another seller's: manage_any_booking.

Scope

crm:write

Permission

Edit in the module

MCP tool

crm_booking_settings_updateOn the full surface; on the compact one, mb_execute_operation with id: "crm.booking.settings.update".

Declared cost: up to 2 reads and 1 writes per call (they count against the daily quota).

Parameters

Response

Errors

Example

curl -X PATCH "https://api.mb-suite.com/v1/crm/booking/settings/{user_id}" \
  -H "Authorization: Bearer $MB_API_KEY"

Try it with your test API key

With a test API key the request always goes to your practice organization: example data you can reset.

curl -X PATCH "https://api.mb-suite.com/v1/crm/booking/settings/{user_id}" \
  -H "Authorization: Bearer $MB_TEST_KEY"

Turn a seller's public booking on or off

crm.booking.settings.set_enabled

The master switch of a seller's public booking (off by default). Turning it on also gives them a default schedule, a public slug and a '30-minute meeting' event type when they have none, so the page works right away; off hides the page and rejects new bookings (existing ones stay). Idempotent. Own: manage_own_booking; another seller's: manage_any_booking.

Scope

crm:write

Permission

Edit in the module

MCP tool

crm_booking_settings_set_enabledOn the full surface; on the compact one, mb_execute_operation with id: "crm.booking.settings.set_enabled".

Declared cost: up to 50 reads and 4 writes per call (they count against the daily quota).

Parameters

Response

Errors

Example

curl -X POST "https://api.mb-suite.com/v1/crm/booking/settings/{user_id}/enabled" \
  -H "Authorization: Bearer $MB_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "enabled": true
}'

Try it with your test API key

With a test API key the request always goes to your practice organization: example data you can reset.

curl -X POST "https://api.mb-suite.com/v1/crm/booking/settings/{user_id}/enabled" \
  -H "Authorization: Bearer $MB_TEST_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "enabled": true
}'

Set a seller's public booking slug

crm.booking.settings.set_slug

Sets the slug of a seller's public booking page (/book/{org}/{slug}): unique in the organization, lowercase letters, digits and dashes, starting with a letter, some words reserved. The previous slug is released. Links shared with the old slug stop working. Own: manage_own_booking; another seller's: manage_any_booking.

Scope

crm:write

Permission

Edit in the module

MCP tool

crm_booking_settings_set_slugOn the full surface; on the compact one, mb_execute_operation with id: "crm.booking.settings.set_slug".

Declared cost: up to 25 reads and 3 writes per call (they count against the daily quota).

Parameters

Response

Errors

Example

curl -X POST "https://api.mb-suite.com/v1/crm/booking/settings/{user_id}/slug" \
  -H "Authorization: Bearer $MB_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "slug": "SLUG"
}'

Try it with your test API key

With a test API key the request always goes to your practice organization: example data you can reset.

curl -X POST "https://api.mb-suite.com/v1/crm/booking/settings/{user_id}/slug" \
  -H "Authorization: Bearer $MB_TEST_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "slug": "SLUG"
}'

Use the seller's profile photo on their booking page

crm.booking.settings.use_profile_photo

Copies the seller's MB Suite profile photo to public storage and sets it as their booking page avatar, so it shows in link previews and to anonymous visitors. A Google Workspace photo cannot be fetched (profile_photo_not_public: upload one instead); no photo answers profile_photo_missing. Own: manage_own_booking; another seller's: manage_any_booking.

Scope

crm:write

Permission

Edit in the module

MCP tool

crm_booking_settings_use_profile_photoOn the full surface; on the compact one, mb_execute_operation with id: "crm.booking.settings.use_profile_photo".

Declared cost: up to 3 reads and 1 writes per call (they count against the daily quota).

Parameters

Response

Errors

Example

curl -X POST "https://api.mb-suite.com/v1/crm/booking/settings/{user_id}/profile-photo" \
  -H "Authorization: Bearer $MB_API_KEY"

Try it with your test API key

With a test API key the request always goes to your practice organization: example data you can reset.

curl -X POST "https://api.mb-suite.com/v1/crm/booking/settings/{user_id}/profile-photo" \
  -H "Authorization: Bearer $MB_TEST_KEY"

List a seller's free booking slots for an event type

crm.booking.availability

Returns the free slots of one of a seller's booking event types between from and to (ms UTC; default: from now for 14 days; at most 31 days per call), computed by the same engine as the public booking page and the AI Setter: the event type's schedule (or the seller's), blocked dates, minimum notice, maximum advance, buffers, the daily cap, the seller's confirmed bookings and the busy times of their connected Google or Outlook calendar (best effort: with calendar_connected false, or if their calendar does not answer, the slots cannot account for it). Pick the event type by event_type_id, or by event_type_slug with vendor_user_id (default: the caller). Each slot has start_ms and end_ms (UTC), start_local in time_zone (the booker's IANA zone; default: the seller's) and start_local_vendor; book one by passing its start_ms to crm.bookings.create. At most limit slots (default 100, up to 500); has_more says there are more in the window: ask again from the last end_ms. Nothing is booked or held. Errors: booking_unavailable (409, details.reason vendor_not_configured, vendor_booking_disabled or event_type_disabled), booking_event_type_not_found, event_type_not_of_vendor, invalid_timezone, invalid_time_range. Your own slots need view_own_bookings; another seller's, view_any_booking (owners, admins, CRM admins and sales managers).

Scope

crm:read

Permission

View the module

MCP tool

crm_booking_availabilityOn the full surface; on the compact one, mb_execute_operation with id: "crm.booking.availability".

Declared cost: up to 300 reads and 0 writes per call (they count against the daily quota). Touches an external platform (google): it counts against the external operations quota.

Parameters

Response

Errors

Example

curl "https://api.mb-suite.com/v1/crm/booking/availability" \
  -H "Authorization: Bearer $MB_API_KEY"

Try it with your test API key

With a test API key the request always goes to your practice organization: example data you can reset. In the practice organization this operation is not simulated (it reaches another platform): it answers 409 sandbox_external_unavailable.