Bulk invite users to the entity
POST/users/invitations/bulk
Validates all invitations all-or-nothing, then creates and sends each
one. If any item fails validation, the entire request is rejected with
a single 400 whose additionalData field contains the full list of
per-item failures (BulkInvitationValidationFailure[]).
On success, per-item status is CREATED (new invitation) or EXISTING
(idempotent hit on a pending invitation for the same email).
When the entity requires dual-auth, the whole batch is validated then
held behind a single pending approval — nothing is sent — and the
response is 202 with the approval's UUID instead of the 201 item
list. Approving that request replays every send.
Maximum 50 invitations per request (hard-coded request limit) and
additionally gated by maxBulkInvitations config.
Requires USER_CREATE permission.
Request
Responses
- 201
- 202
- 400
- 401
- 403
All invitations processed and sent directly (dual-auth off)
Dual-auth on: the batch is held behind a pending approval
RBAC_BULK_INVITE_VALIDATION_FAILED — one or more items failed
validation; additionalData contains List
Missing/invalid JWT or entity selection
Caller lacks USER_CREATE permission