Meeting Prep Settings
The workspace's own instructions added to every meeting prep.
API key access
calls:read scope with an API key (ro_pat_...). A signed-in session uses the caller's role./api/v1/meeting-prep/settingsAccess token from /api/v1/auth/login, or an API key (ro_pat_..., RO-176) from /api/v1/workspaces/current/api-keys: the key implies its workspace and needs the route's scope. MCP connectors (/api/v1/mcp only) may use an OAuth access token (ro_oat_..., RO-284).
In: header
Header Parameters
Id of the workspace to act on (must be a member).
Response Body
curl -X GET "http://localhost:8000/api/v1/meeting-prep/settings" \ -H "X-Workspace-Id: string"{
"prompt": "string",
"max_length": 0,
"auto_prepare": true,
"updated_at": "2019-08-24T14:15:22Z"
}Update My Profile
Change your name, time zone, locale, theme, appearance (RO-355: `appearance` keys are merged into the saved ones; a read returns all of them with defaults) or sidebar pins (RO-310: `pinned_pages` replaces the list). The email can't be changed here (422 `extra_forbidden`) until email verification exists.
Meeting Prep
A booked meeting and the Meeting copilot's prep for it (who, why they replied, prior emails, calls and notes, open questions, a suggested agenda) - `prep: null` until one is written with `POST /ai/meeting-prep`.