POST /calendar_events
returns, and what a meeting from a calendar carries as its
calendar_event: the same object, with the same cev_ id. There is one per meeting. Every member
who has the event on their calendar shares it, so a push for any of them returns it. Its times, link
and title are the meeting’s; its people come from the organizer’s copy. See
Push calendar events.
Attributes
string
Beginning with
cev_. One per meeting; stays the same through reschedules and every member’s
push.string
Always
calendar_event.string
The meeting of this occurrence, beginning with
mtg_.string | null
The iCal UID shared by every attendee’s copy of the event, or
null when the calendar sent none.boolean | null
Whether the event is an occurrence of a recurring series, or
null when it is unknown.string | null
The event title.
string | null
Scheduled start, in ISO 8601.
string | null
Scheduled end, in ISO 8601.
string | null
The link to join the call, or
null when the event has none.object | null
Who organizes the event, or
null when unknown.object[]
Everyone on the invite, the organizer included. Empty once no member has the event.
string
Where the event came from.
calendar_connection: a calendar the member connected.calendar_sync: an event you pushed withPOST /calendar_events.
object
Your key-value pairs, set with
POST /calendar_events and merged on every push ("" removes a
key, metadata: "" removes them all). Shared by every member’s push of the event; never copied to
the meeting. See metadata.string | null
When the event was cancelled, once no member of the workspace still has it; otherwise
null.string
When the event first appeared, in ISO 8601.
string
When the event or its meeting last changed, in ISO 8601.