AI

Prepare Meeting

Write (or refresh) the prep of a booked meeting from our own records.

API key access

Needs the calls:write scope with an API key (ro_pat_...). A signed-in session uses the caller's role.
POST/api/v1/ai/meeting-prep
AuthorizationBearer <token>

Access 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

X-Workspace-Id?X-Workspace-Id

Id of the workspace to act on (must be a member).

meeting_idMeeting Id

The booked meeting to prepare.

Length1 <= length <= 64

Response Body

curl -X POST "http://localhost:8000/api/v1/ai/meeting-prep" \  -H "X-Workspace-Id: string" \  -H "Content-Type: application/json" \  -d '{    "meeting_id": "string"  }'
{
  "meeting_id": "string",
  "prep": {
    "summary": "string",
    "who": "string",
    "why_now": "string",
    "history": [
      "string"
    ],
    "open_questions": [
      "string"
    ],
    "agenda": [
      "string"
    ],
    "talking_points": [
      "string"
    ],
    "risks": [
      "string"
    ],
    "sources": [
      {
        "kind": "string",
        "label": "string",
        "at": "string"
      }
    ]
  },
  "prompt_id": "string",
  "model": "string"
}
Empty
Empty
{
  "detail": [
    {
      "loc": [
        "string"
      ],
      "msg": "string",
      "type": "string",
      "input": null,
      "ctx": {}
    }
  ]
}
Empty
Empty