IdentityInviteResponseDto
Example
JSON
{ "id": "string", "email": "string", "intent": "activate", "first_name": "string", "last_name": "string", "name": "string", "role_id": "string", "node_id": "string", "node_name": "string", "organization_node_id": "string", "effective_from": "2026-04-20T12:00:00.000Z", "effective_to": "2026-04-20T12:00:00.000Z", "has_initial_assignment": false, "status": "pending", "expires_at": "2026-04-20T12:00:00.000Z", "invited_by": "string", "invited_by_identity_id": "string", "created_at": "2026-04-20T12:00:00.000Z" }
Properties
Final intent stamped on the invite at create time. `activate` is the auto-derived default for net-new identities; `add_to_app` is auto-derived when the email matches an existing account-level identity that has no membership in this App; `password_reset` is admin-explicit. `onboard` may appear on rows created before the rename.
The organization the invitation joins, when `node_id` is an organization node or sits beneath one.
The customer's own administrator who sent it with their identity token; `invited_by` names a platform user instead.
Tell us how we can improve this guide.