Update Invites

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}}", " persona" " {{random personna}} ", "industry" " {{random industry}} ", "function" " {{random function}} ", "custom fields attributes" \[ { "key" " {{ random key 1}}", "value" " {{ random value 1}}" }, { "key" " {{ random key 2}}", "value" "{{ random value 2}}" } ], "interest categories" \[ { "name" " {{random category}} ", "interests" \[ { "name" " {{random interest}} ", "intent ids" \[1,2,4,6] }, { "name" " {{random interest}} ", "intent ids" \[1,4] }, { "name" " {{random interest}} " } ] } ] }, "import interest selections" true, "import identity selections" true } } required attributes external email (string / supports accents and special characters) seats (number / see notes for more information) import interest selections these attributes by default are false however, if these are not set to true, any interests/ intents and identity data (personas, function, industry) won't get updated or created import identity selections these attributes by default are false however, if these are not set to true, any interests/ intents and identity data (personas, function, industry) won't get updated or created 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) 03 matchmaking and identities prefilling there are two attributes, which need to be set to "true" import interest selections import identity selections if the interests/ identities don't exist in the matchmaking set up, the api call will create these interests and identities if you make an api call where the interests array or any of those parameters is empty, it will delete them from the invite it will never delete interests or identities from the event itself, since multiple attendees might be using these interests and identity data in the event if the parameters "interest categories" , "persona" , "industry" and "function" are not present in the request (i e you don't have these attributes at all), they won't be updated to specify intents for a specific mm interest, you need to use "intent ids" that correspond to the following intents 1 = networking 2,3 = trading 2 = exploring getting or buying 3 = offer or sell this 4,5 = recruitment 4 = get a job in this 5 = offer a job in this 6,7 = investment 6 = get investment in this 7 = invest in this 8,9 = mentoring 8 = find a mentor 9 = be a mentor if you want to include both intents within a pair, you need to add both " intent ids " in the array if you don't specify the " intent ids " array inside the interest object, all intents will get selected by default 04 custom fields attributes in order to pass this value through the api, you first need to create the custom field under custom content > custom fields the field name can be any values that is easy for you to recognize the field key will be the parameters in your api body request for now, the custom field can only be assigned to the invites