Create User API fields, milestone submission forms, and widget display settings
The Create User API takes optional profile fields, the milestone submission form is configurable, and the widget's dashboard view gets its own display settings.
01 ·Optional fields in the Create User API
The Create User API accepts optional fields alongside the required ones: phone number, country, and any custom fields defined on the server. Custom fields can be numerical, boolean, text, or date-time. Each optional field is validated on input: phone number accepts numeric characters only, country must match a value from the country list, where the casing does not have to be exact, and a custom field that does not exist on the server returns an error naming the field. When a user is created with these fields, the values appear in the user list settings, so the record is complete from first creation.
API-based user onboarding often pulls from a broker's CRM or account-opening system, where records already carry phone, country, and custom profile data. Passing those fields in the creation call means the trader's profile is populated from day one, with no separate sync step.
02 ·Configure the milestone submission form
The milestone submission form is configurable per custom condition. When a custom condition is set (for example, Leave a Trustpilot Review), an admin can open its settings and write custom instructions, with the condition name filling that field by default. The form has two default fields, attach files and message to admins, both on by default; each can be toggled off individually, though the last remaining field stays locked to keep at least one active. Any field can be marked required, which shows a red asterisk on the trader-facing form and must be filled before the form submits. Fields can be reordered using grip icons, and admins can add custom fields of type text or attachment, which appear in the form order and have their own delete confirmation.
Milestone submissions vary in what they need to collect. A review submission might only need a file; a feedback submission might need both text and a file. Configuring the form per condition means traders see only the fields relevant to their task, with instructions written for that specific milestone stage.
03 ·Independent display settings for the milestone widget's dashboard view
When a milestone widget uses the dashboard view, a new Customise Display Settings option separates the widget's appearance from the base milestone settings. The default, Use Milestone Display Settings, keeps behaviour as before. Switching to Customise Display Settings reveals two collapsible sections, Milestone Group and Milestone Stage. Inside Milestone Stage, three sub-sections (Stage Details, Rewards, and Conditions) can be reordered with grip icons. The Stage Details section has a progress stepper option with three size choices, and the stepper's orientation follows the list view's horizontal or vertical setting. The Rewards section shows only the reward types enabled across the milestone groups in the widget, and the Conditions section lets admins toggle conditions per milestone group and choose between showing them in full or collapsing them into an expandable dropdown.
The milestone widget gets placed across different broker surfaces. A sidebar might need a tighter layout than a dedicated milestone page does. Independent display settings mean a broker can tune each widget's output without touching the underlying milestone configuration.
The online-users API endpoint returns results faster for large communities.
14 JanThe preview panel on the Login & Registration settings page now sticks to the top as the page scrolls, while the left panel scrolls independently.
14 Jan