Add many people
Up to 200 people at once (#2716) with the settings of one add (see Add people): each row is added in order by the single add, in its own transaction with its own seat check, emails and audit entry; never all or nothing. A row that fails (no seats left, an invalid email, a member twice in the list) is reported and the rest are still added. A payment link needs each guest's email (a member's is their account's); send_email emails the ticket to those with an address and skips the rest. A refusal about the settings (unknown_ticket_type, free_ticket, wrong_day, ...) stops the batch: before anyone is added it is the answer, as the single add's would be; after, the rows left fail with it. With Idempotency-Key each row is kept under <key>:bulk:<index>, so a retried batch answers what each row made and adds nobody twice (a row that failed is tried again). Rate limited per account: ten batches in ten minutes, with the guest-invite bulk add.
Authorizations
In the browser, authentication rides on the httpOnly session cookies set by /cognito/signin or the Google / Apple sign-in at /cognito/oauth/{provider}. For scripts and for Swagger UI testing, paste an API key (fh_live_…, created with POST /api-keys); a Cognito JWT is accepted too. Sign-in does not return a token in its body.
Parameters
Header Parameters
Optional (#2709): 16 to 200 of [A-Za-z0-9_.:-], a uuid. Kept two days, scoped to the endpoint, the event and the caller.
"^[A-Za-z0-9_.:-]{16,200}$"Path Parameters
The event's id.
"uuid"Request Body
Responses
Each row's result, in order.