The Meetings API provides a powerful mechanism to capture notes, provide talking points or track action items from both 1:1 and group meetings. It does not provide functionality to record or host meetings.
Create meeting
post
Authorizations
AuthorizationstringRequired
Bearer authentication header of the form Bearer <token>.
Body
namestringRequired
typestringRequired
recurringbooleanOptional
Responses
201
Created
application/json
400
Bad Request – invalid request payload.
401
Unauthorized – missing or invalid JWT.
403
Forbidden – insufficient permissions.
404
Not Found – no Entity with that ID.
post
/api/v1/meeting
Get meeting
get
Authorizations
AuthorizationstringRequired
Bearer authentication header of the form Bearer <token>.
Path parameters
idstringRequired
Responses
200
OK
application/json
400
Bad Request – invalid request payload.
401
Unauthorized – missing or invalid JWT.
403
Forbidden – insufficient permissions.
404
Not Found – no Entity with that ID.
get
/api/v1/meeting/{id}
Update meeting
patch
Authorizations
AuthorizationstringRequired
Bearer authentication header of the form Bearer <token>.
Path parameters
idstringRequired
Body
namestringRequired
typestringRequired
recurringbooleanOptional
Responses
200
OK
application/json
400
Bad Request – invalid request payload.
401
Unauthorized – missing or invalid JWT.
403
Forbidden – insufficient permissions.
404
Not Found – no Entity with that ID.
patch
/api/v1/meeting/{id}
Add participant to meeting
post
Authorizations
AuthorizationstringRequired
Bearer authentication header of the form Bearer <token>.
Path parameters
meetingIdstringRequired
Body
entityIdOrEmailstringRequired
Responses
200
OK
application/json
400
Bad Request – invalid request payload.
401
Unauthorized – missing or invalid JWT.
403
Forbidden – insufficient permissions.
404
Not Found – no Entity with that ID.
post
/api/v1/meeting/{meetingId}/participant
Remove participant from meeting
delete
Authorizations
AuthorizationstringRequired
Bearer authentication header of the form Bearer <token>.