Skip to main content
PATCH
Update pending attendee

Headers

x-attendee-pending-edit-token
string

Edit token returned by POST. Required here or as an editToken body field.

Path Parameters

id
number
required

The unique identifier of the pending attendee record

Body

application/json

Updated attendee information

notes
object
required

An object containing attendee form entries.

companyId
string<uuid>
required
email
string<email>

Attendee email address. Required for all standard bookings. Optional only when BookingDto.phoneOnlyBooking is true. Validated as email format when provided.

firstname
string

Either fullname or firstname/lastname is required

Maximum string length: 150
lastname
string

Either fullname or firstname/lastname is required

Maximum string length: 150
fullname
string

Either fullname or firstname/lastname is required

Maximum string length: 150
bringalongEmails
string<email>[]

Additional attendee emails (max 5)

Maximum array length: 5
billingDetails
object | null

Billing details from the booking page's billing block, shown when the meeting type sets meetingPaymentInfo.collectBillingDetails.

useSavedBillingDetails
boolean

The booker chose "I have booked before" instead of typing the billing block again. The server copies the latest details this email left with the same company onto the booking and never sends them back.

phone
string
language
enum<string>
Available options:
en,
de,
fr,
es,
no,
nl,
it,
pl,
se,
tr,
da,
pt,
ru,
uk
timezone
string
dataPolicyAccepted
boolean
editToken
string

Edit token. On PATCH it authorises the update (alternative to the x-attendee-pending-edit-token header). On POST a caller may supply its own (43 to 128 base64url characters); otherwise the api issues one in that response header. Never stored as lead data.

Maximum string length: 128

Response

Pending attendee updated successfully

The response is of type number.