Skip to Content
The Makinari API repo now includes an MCP Server — connect your AI models directly. View on GitHub →
MCP ServerToolsSchedulingPOST

Scheduling

Manage scheduling. Use action=“check_availability” to get available slots (requires date, duration, timezone, team_id). Use action=“schedule” to schedule an appointment (requires title, start_datetime, duration, timezone, context_id).

Input Schema

ParameterTypeDescription
actionstringAction to perform: check_availability or schedule. Enum: check_availability, schedule
datestringDate in YYYY-MM-DD format
durationnumberMeeting duration in minutes (min 15 for check, min 5 for schedule)
timezonestringTimezone (e.g. America/New_York)
team_idstringTeam UUID (required for check_availability)
start_timestringDay start time (default 09:00)
end_timestringDay end time (default 17:00)
participantsarrayParticipant IDs to check availability
resourcesarrayResource IDs
titlestringAppointment title
start_datetimestringStart datetime ISO 8601
context_idstringContext ID (lead_id, site_id, or similar)
locationstringLocation
descriptionstringDescription
remindernumberReminder minutes before

REST Endpoint

Actions map to sub-routes: check_availability/availability, schedule/schedule.

POST /api/agents/tools/scheduling/availability POST /api/agents/tools/scheduling/schedule

Check availability:

POST /api/agents/tools/scheduling/availability Authorization: Bearer YOUR_API_KEY Content-Type: application/json { "date": "2026-03-10", "duration": 30, "timezone": "America/New_York", "team_id": "TEAM_UUID" }

Schedule an appointment:

POST /api/agents/tools/scheduling/schedule Authorization: Bearer YOUR_API_KEY Content-Type: application/json { "title": "Product Demo", "start_datetime": "2026-03-10T14:00:00-05:00", "duration": 30, "timezone": "America/New_York", "context_id": "LEAD_UUID" }

Response:

{ "success": true, "appointment": { "id": "...", "title": "Product Demo", "start_datetime": "2026-03-10T14:00:00-05:00" } }
Last updated on