import requests
url = "https://eu.app.clarifeye.ai/api/v1/projects/{project_id}/meetings/{meeting_id}/transcript/"
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}/transcript/', 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}/transcript/ \
--header 'Authorization: Bearer <token>'{
"results": [
{
"id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
"participant_id": "<string>",
"speaker": "<string>",
"text": "<string>",
"start_ms": 123,
"end_ms": 123,
"started_at": "2023-11-07T05:31:56Z"
}
],
"has_more": true,
"cursor": "<string>",
"source": "live"
}Meeting transcript
The meeting’s transcript, for delta polling: pass back the cursor of the previous page
to get what arrived since. While the call runs these are the utterances heard live
(source: live), paged by arrival: overlapping speakers mean a line can arrive after a
later-starting one, so clients merge by id and sort by start_ms. Once post-call has
rebuilt the transcript from the provider’s recording it is served instead
(source: final), from the top whatever cursor is passed; a client that sees source
change replaces what it holds. It is complete even if live delivery dropped, and is the
same text the meeting’s conversation holds.
import requests
url = "https://eu.app.clarifeye.ai/api/v1/projects/{project_id}/meetings/{meeting_id}/transcript/"
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}/transcript/', 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}/transcript/ \
--header 'Authorization: Bearer <token>'{
"results": [
{
"id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
"participant_id": "<string>",
"speaker": "<string>",
"text": "<string>",
"start_ms": 123,
"end_ms": 123,
"started_at": "2023-11-07T05:31:56Z"
}
],
"has_more": true,
"cursor": "<string>",
"source": "live"
}Authorizations
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
The cursor of the previous page; omit for the start.