Invites

Update invite

2min
Update an existing invite in an event
PATCH
Request
Path Params
{organizationId}
required
Number
The id of the Brella organization you are trying to retrieve data from
{eventId}
required
Number
The id of the Brella event you are trying to retrieve data from
{inviteId}
required
Number
The id of the invite you want to update
Header Parameters
Brella-API-Access-Token
required
String
Your unique Brella API key
Accept
required
String
application/vnd.brella.v4+json
Content-Type
required
String
application/json
Curl
Responses
200


REQUEST BODY

{ "event_invite": { "external_email": "{{random_email}}", "external_id": "{{random_ext_uuid}}", "external_first_name": "{{random_first_name}}", "external_last_name": "{{random_last_name}}", "seats": 1, "external_company": "{{random_company}}", "external_title": "{{random_title}}", "attendee_group_id": "{{user_group_id}}" } }

Required attributes:

  • external_email (String / supports accents and special characters)
  • seats (Number / see notes for more information)

Notes:

01: While multi-seat invites are supported (meaning that the same invite code / URL can be used multiple times to allow different attendees to join the platform), we typically recommend that 1 ticket = 1 invite (so, passing the value 1 to seats), especially if your event uses QR code scanning and / or 3rd party badge printing (eg: xTag, Ticket Butler, Noodle Live etc.)

02: The attendee_group_id attribute is used to map different ticket types / attendee privileges to Brella's user groups, which allow you to control networking privileges, session access privileges and more. You can create as many user groups as needed in the Admin Panel of your event (Event > People > Groups). The attendee_group_id values for the created groups are visible in the Admin Panel as well (see screenshot below). If a value is not specified in the request, the invite will be added to a default user group in Brella (depending on the event type selected).

Updated 20 Apr 2023
Did this page help you?