Skip to main content
POST
Reset member info

Restrictions

Usage

  • Identify the member with one of member_id, member_name, email, phone, or ref_id. If multiple identifiers are present, the server checks them in that order.
  • The caller must be the account owner, the member themself, or hold the Admin role; otherwise the call returns 403 AccessDenied.
  • Put the fields to write under updates: member_name, password, phone, country_code, email, avatar, locale, time_zone, or ref_id. Omitted or null fields keep their current value; updates must carry at least one field.
  • A new member_name, email, or phone must not belong to another member of the account; a conflict returns 400. A changed email or phone is marked unverified unless from is api, the account has member invitations disabled, and the member is not the caller.
  • updates.time_zone set to an empty string clears the member’s own time zone, so the member follows the account’s.
  • updates.country_code is an ISO 3166-1 alpha-2 region code (e.g. “CN”, “US”). It is an independently updatable field: updates.phone is 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.phone has no ”+” prefix, it is parsed with updates.country_code as 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_code is only a parsing hint for the identifying phone; it is never stored.
  • Fields are written one at a time; if a later field fails validation, the fields written before it in the same call stay saved.
  • Members provisioned through SSO cannot be changed while the SSO configuration marks them non-editable or the account has no active SSO configuration.
  • Concurrent profile updates or invitations in the same account can return 429 RequestTooFrequently; retry after a moment.
  • Every call is recorded in the account audit log. Don’t put secrets in request fields.

Authorizations

app_key
string
query
required

APP Key created in the Flashduty console under My → APP Key. Send it as the app_key query parameter or in the Fd-App-Key request header. Its effective access is the intersection of the key's permission scope and the creator's current role permissions. Keep it secret.

Body

application/json

Reset member info request. Top-level fields identify the member, and updates contains the profile fields to write.

member_id
integer<uint64>
required

Member ID used to identify the member.

updates
object
required

New profile values to write. Must include at least one field.

member_name
string

Member name used to identify the member.

email
string

Email address used to identify the member.

phone
string

Phone number used to identify the member. Include country_code when the number is not in E.164 format.

country_code
string

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.

ref_id
string

External reference ID used to identify the member.

from
string

Set to api to mark an updated phone or email as verified. Only takes effect when the account has member invites disabled and the member is not the caller; 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.

request_id
string
required

Unique ID for this request. Mirrored in the Flashcat-Request-Id response header. Include it when reporting issues.

Example:

"01HK8XQE3Z7JM2NTFQ5YJ8P9R4"

data
object

Empty response