Update Event
Authentication
Bearer authentication of the form Bearer <token>, where token is your auth token.
Path parameters
Request
Returned as the doors have it (see EventPhase): DRAFT for an event
waiting for a host, LIVE for one scheduled or open, ENDED for one that
is over, even in the few minutes before it is marked so and its
overage settled. The times open and close an event by themselves, so
a host sets a status only to start one with no time to open at (LIVE),
to end one early (ENDED), or to reopen one (LIVE). Reopening an event
whose last window has closed clears its endsAt and
questionsCloseAt; setting ENDED settles the overage.
Defaults to PUBLIC on create; left alone on update.
Replaces the domains a DOMAIN event lets in, at most 20; @ and
whole addresses are trimmed to their domain. Each must be on the
workspace’s allow-list, or already be one of the event’s: otherwise
422 domain_not_allowed, with the domains in details.domains.
Empty means the whole allow-list, including domains added to it
later; listing every domain on it instead fixes the choice to
those. Left out on update, the list is left alone.
For a DOMAIN event: take Google sign-in only, and send no codes.
False on create; left alone on update. Stored as sent, but a
workspace that requires Google sign-in makes every event Google
only whatever this says.
An IANA zone this server knows (a 422 otherwise), or null for none.
The Zoom, Google Meet or Microsoft Teams call the event runs
beside, as an https join link. For example: a Zoom meeting, webinar
or personal room (zoom.us/j/…, /w/…, /my/…, on zoom.us,
zoom.com or zoomgov.com and their regional hosts such as
us02web.zoom.us); a Meet code (meet.google.com/abc-defg-hij);
or a Teams meeting (teams.microsoft.com/l/meetup-join/… or
/meet/…, on teams.microsoft.com, teams.live.com,
teams.cloud.microsoft or the government clouds). A link still
wrapped in Outlook’s Safe Links is unwrapped. Anything else, or a
Zoom start link (/s/…), is refused (422). Empty or null clears it.
Whether “Powered by taktoria.com” shows on the event’s way in: the door and the join form. True on create; left alone on update.
Presenter screen background, #rrggbb (or #rgb).
Presenter screen accent, #rrggbb (or #rgb).
Response
Returned as the doors have it (see EventPhase): DRAFT for an event
waiting for a host, LIVE for one scheduled or open, ENDED for one that
is over, even in the few minutes before it is marked so and its
overage settled. The times open and close an event by themselves, so
a host sets a status only to start one with no time to open at (LIVE),
to end one early (ENDED), or to reopen one (LIVE). Reopening an event
whose last window has closed clears its endsAt and
questionsCloseAt; setting ENDED settles the overage.
Where the event stands right now, from its times first: it opens at the
earlier of startsAt and questionsOpenAt, and ends at the later of
endsAt and questionsCloseAt, with nobody having to start it.
Who may join. Separate from settings, which describes how the room
behaves once somebody is in it rather than whether they get in.
The email domains a DOMAIN event chose from the workspace’s
allow-list, such as acme.com. Only those still on it count; empty
means the whole allow-list (see /partner-domains).
For a DOMAIN event: an address counts only when proved by signing
in with Google, never by an emailed code. The rule as it applies:
true whenever the workspace requires Google sign-in, whatever was
set on the event.
Whether attendees must type a passcode as well as the code. The
passcode itself is never returned; set it with passcode.
When the event starts: it opens by itself then (or at
questionsOpenAt, if that is earlier), and is scheduled until it
does. With neither, it waits for a host to start it.
When the event ends, unless questionsCloseAt is later: from the
later of the two it is ended, and within five minutes it is marked
ENDED and its overage settled, as ending it by hand does.
When questions stop. If it is after endsAt, the event stays open
until then; before it, the event runs on to its end with no new
questions.
IANA zone the event’s times are written in and shown in, such as
Europe/Berlin. Absent for none, where the app shows the times in
the workspace’s default zone, else UTC. The times themselves are
absolute either way.
The Zoom, Google Meet or Microsoft Teams call the event runs beside, as its join link. Shown to hosts and to the attendees the event lets in; Dory’s app inside that meeting opens this event.
What the workspace was paying for per event when this one was settled. Absent until then: it is copied onto the event so that raising the plan later cannot rewrite an invoice already sent.