Request custom fields in the user API, and a language-change webhook
The user-data API can now return chosen custom fields on request, and a new webhook fires when a trader changes their language.
01 ·Ask the user API for the custom fields you need
The user-data lookup can now take an optional list of custom profile fields to return alongside the standard account data. The fields asked for are checked against what the community has set up before any values come back. Leave the list out and the response carries just the default fields, so an everyday lookup stays light and only the calls that need extra data carry it.
A broker syncing trader data into a CRM or BI tool can pull exactly the custom fields that system needs in one call, which keeps the integration lean and avoids hauling back data it will not use.
02 ·Know when a trader changes language
A new outgoing webhook fires whenever a trader changes their community language. The event carries the trader's identity, the old and new language, the time it changed, and the community it happened in, so a broker's own systems get a live signal to act on without polling for it.
A broker serving traders across regions can react to a language switch as it happens, routing the right localised follow-up or support without combing through accounts one by one.
On mobile, the chat input bar now keeps its background, closing the gap that showed between a quoted message and the input when replying.
3 DecServer lookups on large communities are now more efficient, avoiding a memory limit that could slow responses on the busiest platforms.
3 Dec