Reset member info
Identify a member and reset the specified profile fields.
Restrictions
Usage
- Identify the member with one of
member_id,member_name,email,phone, orref_id. If multiple identifiers are present, the server checks them in that order. updates.country_codeis an ISO 3166-1 alpha-2 region code (e.g. “CN”, “US”). It is an independently updatable field:updates.phoneis not required, and the new region is stored even when the phone is unchanged. An explicit empty string is rejected with a 400.- When
updates.phonehas no ”+” prefix, it is parsed withupdates.country_codeas the region hint, falling back to the member’s stored region and then to “CN”. Legacy digit calling codes such as “86” remain accepted only as parsing hints — stored values are always ISO region codes. - The top-level
country_codeis only a parsing hint for the identifyingphone; it is never stored. - Put the profile fields to write under
updates:member_name,password,phone,country_code,email,avatar,locale,time_zone, orref_id. - Members provisioned by SSO cannot be changed when SSO marks them as externally managed.
updatesmust carry at least one field; an object with every field omitted is rejected.
Authorizations
App key issued from the Flashduty console under Account → APP Keys. Required on every public API call. Keep it secret — it grants the same access as the owning account.
Body
- Option 1
- Option 2
- Option 3
- Option 4
- Option 5
Reset member info request. Top-level fields identify the member, and updates contains the profile fields to write.
Member ID used to identify the member.
New profile values to write. Must include at least one field.
Member name used to identify the member.
Email address used to identify the member.
Phone number used to identify the member. Include country_code when the number is not in E.164 format.
Region hint for parsing phone when it has no "+" prefix — an ISO 3166-1 alpha-2 code such as "CN" (the default when omitted). Legacy digit calling codes like "86" are still accepted in this parsing context.
External reference ID used to identify the member.
Set to api to mark an updated phone or email as verified. Only takes effect when the account has member invites disabled; any other value is ignored.
Response
Success
Success response envelope. On every 2xx response, request_id identifies the call (also mirrored in the Flashcat-Request-Id header) and data holds the endpoint-specific payload. Failure responses use a different shape — see ErrorResponse.