Meetings
Meeting routes manage calendar meetings that are not doctor appointments, including add, edit, get, and delete actions.
Meeting Data
- Meetings can be connected to customers, users, team members, rooms, projects, or notes depending on the route.
- Date/time values should be sent as UTC Y-m-d H:i:s.
- Store meeting_id from add/list responses for edit, get, and delete actions.
Calendar Behavior
- The UI should refresh calendar/list views after add, edit, or delete success.
- Room or reservation conflicts should be checked with availability routes when relevant.
Common Flow
- Load calendar/meeting permissions from User.Basic.
- Create meetings with required title/date fields.
- Open one meeting with Meeting.Get.
- Edit or delete using the saved meeting_id.