Skip to main content
POST
Create a meeting

Authorizations

Authorization
string
header
required

OAuth 2.0 authorization code flow with PKCE (S256). See the authorization guide.

Scopes

meetings:write

Create, update and delete your meetings

Body

application/json
topic
string
required

Nonblank title, trimmed.

Required string length: 1 - 512
start_time
string<date-time>
required

Include a time zone offset. Stored in UTC.

duration_minutes
integer
required
Required range: 1 <= x <= 10080
format
enum<string> | null
Available options:
in_person,
video_call,
phone_call
join_url
string | null

Meeting join link. Null or blank clears it; omitted leaves it unchanged.

Maximum string length: 2048
contact_ids
string<uuid>[]

Accessible client ids, checked before the meeting is created. Set at creation only.

household_ids
string<uuid>[]

Accessible client ids, checked before the meeting is created. Set at creation only.

Response

The saved meeting id.

The saved meeting id. Fetch its detail separately with meetings:read. No artifact or recording read is performed by a write.

id
string<uuid>
required