User Update API

Update user account information using an access token.

Keep account details current and enhance security by updating the email address and password.

This API is available on the Personal plan or higher.

PUT

/api/user/v1/update

HTTP Header 
X-Access-Token: eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...
{
    "eml": "yourchange@gmail.com",
    "pwd": "Zght943!"
}

Request Parameters

eml string
New email address to update.
Re-authentication is required when logging in after changing the email.
pwd string
New password to update.
Must be 6–30 characters long and contain a combination of letters and numbers. 
{
    "code": 0,
    "message": "",
    "result": null
}

Response Parameters

code integer
Response code: 0 = Success, other values = Error
message string
Response message. If the response code is not 0, an error message is returned.
result null

When to Use This API

Use this API when a user needs to update their linked email address or reset their password for security reasons.

It is especially valuable for enforcing periodic password rotation policies in enterprise environments or automating workflows that require user data synchronization.

Things to consider when changing email

Changing an email address is not a simple update.
After the change, users must re-authenticate with the new email, and a new access token must be issued.

When automating email changes, calling additional APIs with the old token immediately after the update may result in authentication errors.

Always call the Authentication API again to obtain a new token before proceeding with subsequent requests.

Password Policy

pwd must be 6–30 characters long and include a combination of letters and numbers. Requests that do not meet this requirement will be rejected.

When updating passwords in automated environments, ensure they are handled securely and never stored in plain text.

Key Points for Production Use

This API is not just a data update. It is a critical API that changes the account’s security state.

Updating email or password directly affects login credentials and authentication flows, and may require follow-up actions such as session invalidation, re-authentication, or security notifications.

Things to consider

Changing an email address directly affects account ownership and should be handled with care.

  • Passwords must be transmitted only over secure channels (HTTPS).
  • Calling this API directly from the client can introduce security risks.
  • Apply a token invalidation policy immediately after the change.
  • Always validate input on the server side.