Reference
Prompter
3 routes, generated from Morse’s own OpenAPI document. Every path below hangs off the base URL, and every one needs the bearer header.
The examples are built from each route’s schema, so the shapes and types are exactly what the API declares. The values are illustrative, and no one has run them.
Who Morse Intelligence answers questions for in this meeting, and which of the meeting's colleagues it could.
GET
/meetings/{meeting_id}/prompterHost only.
GET/meetings/{meeting_id}/prompter
curl "$MORSE/meetings/3f9c1a24-5e6f-4b31-9a77-1b2c3d4e5f60/prompter" \
-H "Authorization: Bearer $MORSE_TOKEN"200
{
"candidates": [
{
"email": "priya@neuralarc.ai",
"name": "Priya Shah",
"user_id": "3f9c1a24-5e6f-4b31-9a77-1b2c3d4e5f60"
}
],
"recipients": [
{
"email": "priya@neuralarc.ai",
"name": "Priya Shah",
"user_id": "3f9c1a24-5e6f-4b31-9a77-1b2c3d4e5f60"
}
]
}Replace who Morse Intelligence answers questions for, by user id.
PUT
/meetings/{meeting_id}/prompterHost only; each must be a colleague of this meeting.
PUT/meetings/{meeting_id}/prompter
curl -X PUT "$MORSE/meetings/3f9c1a24-5e6f-4b31-9a77-1b2c3d4e5f60/prompter" \
-H "Authorization: Bearer $MORSE_TOKEN" \
-H "Content-Type: application/json" \
-d '{ "recipients": [ "…" ] }'200
{
"candidates": [
{
"email": "priya@neuralarc.ai",
"name": "Priya Shah",
"user_id": "3f9c1a24-5e6f-4b31-9a77-1b2c3d4e5f60"
}
],
"recipients": [
{
"email": "priya@neuralarc.ai",
"name": "Priya Shah",
"user_id": "3f9c1a24-5e6f-4b31-9a77-1b2c3d4e5f60"
}
]
}Your answers as they are written: card, answer (the text so far),
done, none, failed, withdrawn.
GET
/meetings/{meeting_id}/prompter/eventsA reconnect gets the meeting's cards back, so nothing said while it was away is lost.
GET/meetings/{meeting_id}/prompter/events
curl "$MORSE/meetings/3f9c1a24-5e6f-4b31-9a77-1b2c3d4e5f60/prompter/events" \
-H "Authorization: Bearer $MORSE_TOKEN"