Skip to main content
POST
Create, change or delete a meeting slot

Authorizations

Authorization
string
header
required

Supabase JWT — Authorization: Bearer <token>.

Body

application/json
action
enum<string>
required

create a slot on a meeting step, update one, or delete one (its booked candidates are cancelled and e-mailed).

Available options:
create,
update,
delete
slot_id
string<uuid>

update / delete: the slot (position_meeting_slot.id).

step_id
string<uuid>

create: the meeting step (position_def_step.id, type meeting).

start_at
string<date-time>

create (required) / update: when the meeting starts. Not in the past.

duration_minutes
integer

Length, 5 to 1440 minutes. Default on create: the step's meeting.duration_minutes, else 30.

Required range: 5 <= x <= 1440
capacity
integer

How many candidates can book it, 1 to 500 (default 1); not below the number already booked.

Required range: 1 <= x <= 500
location
string | null

Address or room; null = the step's location.

Maximum string length: 500
meeting_url
string | null

Video link; null = the step's link.

Maximum string length: 2000
Pattern: ^https?:\/\/\S+$
interviewer_profile_id
string<uuid> | null

Who holds the meeting (profile.id of a user of the company); null = the position's recruiter.

note
string | null

Internal note, not shown to candidates.

Maximum string length: 2000
agenda
string | null

Agenda for the panel (company feature meeting_panels).

Maximum string length: 4000
panel_profile_ids
string<uuid>[] | null

Needs the meeting_panels feature; hand-made slots only: up to 8 users (profile.id) who attend besides the interviewer, who leads. Empty or null removes the panel; left out keeps it.

Maximum array length: 8
dry_run
boolean
default:false

true: validate and answer the slot as it would be and the booked candidates who would be e-mailed, without writing anything.

Response

The slot after the call (or as it would be, in a dry run) and the bookings it reaches.

action
enum<string>
required

The action done (or checked).

Available options:
create,
update,
delete
dry_run
boolean
required

true when nothing was written.

slot
object
required
affected_bookings
object[]
required

Booked candidates this call e-mails (or would, in a dry run). Empty when nobody is told.

warnings
string[]
required

Things the user should know (e.g. booked candidates are not told about a capacity change).