Assistant Context
Who and where (RO-300): the user, the workspace (time zone, local time and date), the role and the credential with its scopes. Any API key or connector may call it.
API key access
/api/v1/assistant/contextAccess 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/assistant/context" \ -H "X-Workspace-Id: string"{
"user": {
"id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
"name": "string",
"email": "string"
},
"workspace": {
"id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
"name": "string",
"timezone": "string",
"plan": "string",
"suspended": true
},
"role": "owner",
"credential": {
"kind": "session",
"name": "string",
"scopes": [
"string"
]
},
"now": "2019-08-24T14:15:22Z",
"local_time": "string",
"today": "2019-08-24"
}Assistant Briefing
A compact daily briefing (RO-300): activity since `since` (default the last 24 hours, at most 31 days back), what needs the user (drafts to review, replies with an open draft, handoff requests) and today's meetings, AI callbacks and calls in the workspace's time zone. An API key or connector sees the sections its scopes can read (`leads:read`, `analytics:read`, `replies:read`, `sequences:read`, `calls:read`); the others are named in `omitted`.
Cancel Assistant Action
Drop a proposed plan (RO-303); nothing is changed.