MB SuiteMB Suite
Menú

Referencia de la API · Perfil

Slug

profile · slug · 2 operaciones

GET/v1/profile/slug/availabilityPOST/v1/profile/slug
GET/v1/profile/slug/availability

Check whether a slug is available

profile.slug.check

LecturaIdempotenteDesde 2026-11-01

Says whether a slug can be used by this organization: available true when it is free or is already this organization's slug (current true), or available false with reason and message: required, too_short, too_long, format (3 to 48 lowercase letters, digits and hyphens, not starting or ending with a hyphen), reserved (words MB Suite uses in its own addresses) or taken (another organization has it: slugs are unique across MB Suite). It changes nothing. Use it before profile.slug.update. Requires view access to the Profile module.

Alcance
profile:read
Permiso
Ver el módulo
Tool del MCP
profile_slug_checkEn la superficie completa; en la compacta, mb_execute_operation con id: "profile.slug.check".

Costo declarado: hasta 2 lecturas y 0 escrituras por llamada (cuentan en el cupo diario).

Parámetros

slugstringqueryrequerido

The slug: 3 to 48 lowercase letters, digits and hyphens, not starting or ending with a hyphen.

Respuesta

slugstring
availableboolean
currentboolean

true when it is already this organization's slug.

reasonenum | null

Valores: required, too_short, too_long, format, reserved, taken

messagestring | null

Errores

invalid_inputunknown_fieldauthentication_requiredscope_insufficientmodule_access_deniedoperation_not_foundrate_limitedquota_exceeded

Ejemplo

curl "https://api.mb-suite.com/v1/profile/slug/availability?slug=SLUG" \
  -H "Authorization: Bearer $MB_API_KEY"

Probar con tu API key de prueba

Con una API key de prueba el pedido va siempre a tu organización de práctica: datos de ejemplo que puedes reiniciar.

curl "https://api.mb-suite.com/v1/profile/slug/availability?slug=SLUG" \
  -H "Authorization: Bearer $MB_TEST_KEY"
POST/v1/profile/slug

Change the organization's slug

profile.slug.update

EscrituraIdempotenteDesde 2026-11-01

Changes the organization's slug, its identifier in the app's addresses (mb-suite.com/<slug>/…) and in the public booking pages of the main domain (mb-suite.com/book/<slug>/…). Every link with the old slug stops working and the old slug becomes available to other organizations; custom domains keep working. Validates like the screen: 400 invalid_slug with details.reason (required, too_short, too_long, format, reserved) and 409 slug_taken when another organization uses it; the uniqueness check and the change are atomic. Sending the current slug changes nothing (changed false). dry_run=true runs the same validations and says what would change without changing it; its preview says needs_confirmation false: running it does not need the confirm_token the dry run returns. Fires profile.slug.changed. Returns slug, previous_slug and changed. Owners and admins only (of the organization or, on an Account, of its workspace).

Instrucciones para agentes

Confirm the change with the person first: every link with the old slug (app bookmarks, public booking links on mb-suite.com) stops working and someone else can take the old slug.

Alcance
profile:write
Permiso
Editar en el módulo · Solo owner, admin
Tool del MCP
profile_slug_updateEn la superficie completa; en la compacta, mb_execute_operation con id: "profile.slug.update".
Eventos que puede emitir
profile.slug.changed

Costo declarado: hasta 4 lecturas y 3 escrituras por llamada (cuentan en el cupo diario).

Parámetros

slugstringcuerporequerido

The slug: 3 to 48 lowercase letters, digits and hyphens, not starting or ending with a hyphen.

Respuesta

slugstring
previous_slugstring
changedboolean

Errores

role_requiredinvalid_inputunknown_fieldauthentication_requiredscope_insufficientcrm_action_deniedidempotency_key_reusedrate_limitedquota_exceeded

Ejemplo

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

Probar con tu API key de prueba

Con una API key de prueba el pedido va siempre a tu organización de práctica: datos de ejemplo que puedes reiniciar.

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