Read saved transcript
const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://api.livefaces.ai/v1/sessions/{session_id}/transcript', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));curl --request GET \
--url https://api.livefaces.ai/v1/sessions/{session_id}/transcript \
--header 'Authorization: Bearer <token>'{
"complete": true,
"text": "<string>"
}{
"code": "<string>",
"detail": "<unknown>",
"request_id": "<string>"
}{
"code": "<string>",
"detail": "<unknown>",
"request_id": "<string>"
}{
"code": "<string>",
"detail": "<unknown>",
"request_id": "<string>"
}{
"code": "<string>",
"detail": "<unknown>",
"request_id": "<string>"
}{
"code": "<string>",
"detail": "<unknown>",
"request_id": "<string>"
}{
"code": "<string>",
"detail": "<unknown>",
"request_id": "<string>"
}Sessions
Read saved transcript
Requires sessions:read and the key that created the session. Availability follows recording settings; saving can lag the live conversation.
GET
/
v1
/
sessions
/
{session_id}
/
transcript
Read saved transcript
const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://api.livefaces.ai/v1/sessions/{session_id}/transcript', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));curl --request GET \
--url https://api.livefaces.ai/v1/sessions/{session_id}/transcript \
--header 'Authorization: Bearer <token>'{
"complete": true,
"text": "<string>"
}{
"code": "<string>",
"detail": "<unknown>",
"request_id": "<string>"
}{
"code": "<string>",
"detail": "<unknown>",
"request_id": "<string>"
}{
"code": "<string>",
"detail": "<unknown>",
"request_id": "<string>"
}{
"code": "<string>",
"detail": "<unknown>",
"request_id": "<string>"
}{
"code": "<string>",
"detail": "<unknown>",
"request_id": "<string>"
}{
"code": "<string>",
"detail": "<unknown>",
"request_id": "<string>"
}Authorizations
Organization API key. Keep it on your server.
Path Parameters
The session id returned by either launch endpoint.
Query Parameters
Use text for a plain-text response, or json for text and completion state.
Available options:
json, text