- 📚 State the two things the Inbox Messaging guide left implicit. A new Prerequisites section lists the
inbox_read / inbox_write scopes and the fact that Inbox Conversations for a Channel only exist once that Channel is connected to the Account — with no connection there is nothing to read and nothing to reply to. Flow now says up front that API messaging is reply-only: threads are opened on the Channel's side, and a Conversation you create yourself is not linked to a Channel's messaging system, so its Messages never reach the guest.
- 📚 Correct how Claude's custom connectors (Cowork, claude.ai, Claude Desktop, mobile) connect to the MCP server: register the bare
https://www.bookingsync.com/mcp URL with no query parameters, leave the OAuth client ID/secret empty, and paste the mcp_… token on the Connect to bookingsync-mcp sign-in page Smily opens — documented in Connecting clients with a screenshot of that page, and in Authentication → Connector sign-in. The pasted token is the credential — there is no separate connector password — so it keeps its own account scoping and expiry, and revoking it stops the connector too, which is why an expired token sends you back through the same page. The ?token= URL parameter is now marked legacy: still accepted, so existing setups keep working, but no longer the way to connect Claude. Troubleshooting covers the sign-in page appearing, a connector asking to reconnect, a rejected token, and Unregistered redirect_uri. (400).
- 📚 Document the per-application connected-accounts cap on private applications. Private apps are limited to 5 connected accounts by default; new installations (both OAuth and
private access code) are blocked once the cap is reached. Partners can contact partners@smily.com to formalize the partnership and lift the cap.
- 📚 Document how the
channel attribute on an Inbox Message controls relay to the originating platform (Airbnb, Booking.com, etc.) and how to derive the right value from the Conversation's default_channel. See the Inbox Messaging guide.
- 📚 Document that
start_at and end_at on Create a new booking must be full datetimes whose time-of-day matches the rental's checkin_time / checkout_time. Date-only values get coerced to midnight and trip the "is within a used period" validation against adjacent bookings. The booking-creation example payloads now use full datetimes instead of START_AT / END_AT placeholders.
- 🛠 Add damage-deposit-related fields
- 🛠 Followup: Add parameters descriptions and enum options
- 📚 Add documentation for api/v3/me
- 🛠 Update dependencies selectively for arm64 support
- 🐛 Fix nested-hash translated attributes documentation mistakes
- 🛠 Discount Codes docs
- 📚 add link to Channel API
- 🛠 [core-5497] Add pet fee
- 📚 Document constraints batch 7
- 📚 Document constraints batch 6
- 📚 Document constraints batch 5
