Your Ask Clara thread on this meeting
import requests
url = "https://eu.app.clarifeye.ai/api/v1/projects/{project_id}/meetings/{meeting_id}/ask/"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text)const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://eu.app.clarifeye.ai/api/v1/projects/{project_id}/meetings/{meeting_id}/ask/', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));curl --request GET \
--url https://eu.app.clarifeye.ai/api/v1/projects/{project_id}/meetings/{meeting_id}/ask/ \
--header 'Authorization: Bearer <token>'{
"id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
"turn_status": "idle",
"turn_error": "<string>",
"turn_events": [
{}
],
"updated_at": "2023-11-07T05:31:56Z",
"chat_history": [
{}
]
}Meetings
Your Ask Clara thread on this meeting
The caller’s private thread of questions to Clara on this meeting (CLA-2059), in the
Work with Clara poll shape plus its chat_history. Every viewer has their own; nobody
else, admins included, can read it. Before the first question: id null, empty history.
While turn_status is running, poll with ?poll=1: the turn state only, without
chat_history.
GET
/
projects
/
{project_id}
/
meetings
/
{meeting_id}
/
ask
/
Your Ask Clara thread on this meeting
import requests
url = "https://eu.app.clarifeye.ai/api/v1/projects/{project_id}/meetings/{meeting_id}/ask/"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text)const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://eu.app.clarifeye.ai/api/v1/projects/{project_id}/meetings/{meeting_id}/ask/', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));curl --request GET \
--url https://eu.app.clarifeye.ai/api/v1/projects/{project_id}/meetings/{meeting_id}/ask/ \
--header 'Authorization: Bearer <token>'{
"id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
"turn_status": "idle",
"turn_error": "<string>",
"turn_events": [
{}
],
"updated_at": "2023-11-07T05:31:56Z",
"chat_history": [
{}
]
}Authorizations
BearerAuthTokenAuth
Use Authorization: Bearer <token>. The token is either a user token / OAuth access
token, or a service-account API key (cfk_...). A key is valid on every endpoint and
acts as its service account, an organization member with per-store permissions.
Refused keys answer 403 with Invalid API key., API key revoked.,
API key expired. or API key disabled..
Query Parameters
Return the turn state only (no chat_history).
Available options:
1