My calendar connections
import requests
url = "https://eu.app.clarifeye.ai/api/v1/users/me/meeting-calendars/"
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/users/me/meeting-calendars/', 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/users/me/meeting-calendars/ \
--header 'Authorization: Bearer <token>'{
"platforms_available": [
"google_calendar"
],
"results": [
{
"id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
"platform": "google_calendar",
"platform_email": "<string>",
"status": "connecting",
"status_detail": "<string>",
"last_synced_at": "2023-11-07T05:31:56Z",
"created_at": "2023-11-07T05:31:56Z"
}
]
}Meetings
My calendar connections
The requesting user’s connected calendars (Google Calendar, Microsoft Outlook) for Clara’s meeting scheduling, and which providers this instance can connect. The refresh token is never stored here — Recall.ai holds it; reconnecting means a fresh consent.
GET
/
users
/
me
/
meeting-calendars
/
My calendar connections
import requests
url = "https://eu.app.clarifeye.ai/api/v1/users/me/meeting-calendars/"
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/users/me/meeting-calendars/', 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/users/me/meeting-calendars/ \
--header 'Authorization: Bearer <token>'{
"platforms_available": [
"google_calendar"
],
"results": [
{
"id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
"platform": "google_calendar",
"platform_email": "<string>",
"status": "connecting",
"status_detail": "<string>",
"last_synced_at": "2023-11-07T05:31:56Z",
"created_at": "2023-11-07T05:31:56Z"
}
]
}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..