Actions120
- Activity Actions
- API Token Actions
- Assessment Actions
- Assessment Comment Actions
- Assessment Phase Actions
- Assessment Section Actions
- Assessment Section Event Actions
- Assessment Section Template Actions
- Assessment Task Set Actions
- Assessment Template Actions
- Assessment Template Checklist Actions
- Assessment User Actions
- Checklist Actions
- Checklist Category Actions
- Checklist Category Template Actions
- Checklist Template Actions
- Client Actions
- Custom Field Actions
- Document Actions
- Finding Actions
- Finding Event Actions
- List finding events
- Create a finding comment
- Update a finding comment
- Create a finding retest
- Update a finding retest
- Create a finding retest inquiry
- Update a retest inquiry
- Create a finding retest cancelled event
- Update a retest cancelled event
- Create a finding review event
- Create a finding retest review event
- Create a remediation status change
- Update a remediation status change
- Finding Layout Actions
- Finding Template Actions
- Language Actions
- Notification Actions
- Output File Actions
- Reaction Actions
- Role Actions
- Snippet Actions
- Tag Actions
- Target Actions
- Task Actions
- Task Set Actions
- Team Actions
- Team User Actions
- Test Case Actions
- Test Case Template Actions
- Theme Actions
- Tool Finding Actions
- Tool Target Actions
- User Actions
User → Create a user
AI-generatedSummary
Creates a Reporter user with the supplied name and email, plus any optional profile, client, role, or custom-field values.
Inputs
- First name (required) — User’s first name (maximum 191 characters).
- Last name (required) — User’s last name (maximum 191 characters).
- Email (required) — User’s valid email address (maximum 191 characters).
- Additional Fields — Optional prefix, suffix, phone, mobile, job title, location, LinkedIn page, client company IDs, and global role IDs. Clients apply to client users; roles grant global access.
- Custom Fields — Optional custom field/value pairs to include for the user.
Output shape
A single API response item for the created user.
The implementation sends the supplied fields in the create-user request body and returns the parsed API response. The source does not establish a more specific response schema.