Start connecting a calendar
import requests
url = "https://eu.app.clarifeye.ai/api/v1/users/me/meeting-calendars/connect/"
payload = { "redirect_back_to": "<string>" }
headers = {
"Authorization": "Bearer <token>",
"Content-Type": "application/json"
}
response = requests.post(url, json=payload, headers=headers)
print(response.text)const options = {
method: 'POST',
headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'},
body: JSON.stringify({redirect_back_to: '<string>'})
};
fetch('https://eu.app.clarifeye.ai/api/v1/users/me/meeting-calendars/connect/', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));curl --request POST \
--url https://eu.app.clarifeye.ai/api/v1/users/me/meeting-calendars/connect/ \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"redirect_back_to": "<string>"
}
'{
"authorize_url": "<string>"
}Meetings
Start connecting a calendar
Returns the provider’s authorize URL for the frontend popup. The provider redirects
to /api/v1/meetings/oauth/callback/, which registers the calendar with Recall.ai and
bounces the popup to the frontend relay page with calendar_connected=1 or
calendar_error=<code>.
POST
/
users
/
me
/
meeting-calendars
/
connect
/
Start connecting a calendar
import requests
url = "https://eu.app.clarifeye.ai/api/v1/users/me/meeting-calendars/connect/"
payload = { "redirect_back_to": "<string>" }
headers = {
"Authorization": "Bearer <token>",
"Content-Type": "application/json"
}
response = requests.post(url, json=payload, headers=headers)
print(response.text)const options = {
method: 'POST',
headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'},
body: JSON.stringify({redirect_back_to: '<string>'})
};
fetch('https://eu.app.clarifeye.ai/api/v1/users/me/meeting-calendars/connect/', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));curl --request POST \
--url https://eu.app.clarifeye.ai/api/v1/users/me/meeting-calendars/connect/ \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"redirect_back_to": "<string>"
}
'{
"authorize_url": "<string>"
}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..
Body
application/json
Response
Authorize URL