GET /v1/user/preferences
Get the current preferences for a user.Authentication
Requires User API Key in theX-API-Key header.
Request
Response
PUT /v1/user/preferences
Update user scheduling preferences.Authentication
Requires User API Key in theX-API-Key header.
Request
Request Body
Response
Preference Fields
object
Work hours for each day of the week. Each day has:
enabled: Whether you work this daystart: Start time in HH:MM format (e.g., “09:00”)end: End time in HH:MM format (e.g., “17:00”)
string
IANA timezone (e.g., “America/New_York”, “Europe/London”)
integer
Minutes of buffer between meetings: 0, 15, or 30
integer
How many days ahead to search for availability (7-90)
integer
Maximum meetings allowed per day (1-10)
string
When you’re most productive:
flexible- No preferencemorning_person- Best before noonafternoon_person- Peak 12-5pmevening_person- Best after 5pm
string
Free-form text describing your preferences. The AI processes this with Claude LLM to generate SmartWeights.Example: “I prefer to keep Fridays meeting-free for deep work. Morning meetings work best for strategic discussions.”
array
Protected time blocks for deep work:
Related Endpoints
Update Preferences (MCP)
MCP tool for updating preferences
AI Learning
How preferences affect AI scheduling