Update user
Updates an existing user's information. This endpoint allows modification of various user properties including password, status, personal information, and account settings. Only include the fields you
Endpoint
PUT/v2/user/{id}
Link
Request
Authentication
An API key is required for authentication. Include it in the Authorization header.
Header:
AuthorizationValue: Your API key token
HTTP Method & URL
Method:
PUTURL:
https://stagep.tst-apidmndelss.com/v2/user/{id}
Path Parameters
id
string
Unique identifier of the user to update.
Yes
user_abc123def
Headers
Authorization
Bearer <JWT>
Yes
Accept
application/json
Yes
Content-Type
application/json
Yes
Request Body (JSON)
Include only the fields you want to update. Omitted fields will remain unchanged.
customerId
string
Associated customer identifier.
No
cust_789xyz
password
string
New login password.
No
NewSecurePass123!
status
string
User status (see values below).
No
ACCEPT
is2fa
boolean
2FA enabled status.
No
true
name
string
User's first name.
No
John
lastname
string
User's last name.
No
Smith
comment
string
Administrative comments.
No
Updated contact info
Status Values
NEW- Registered userREADY_FOR_MODERATION- Ready for reviewMODERATED- Under moderationVERIFY- Verification in progressACCEPT- Approved userREJECT- Rejected userBANNED- Banned user
Example Request Body (Partial Update):
Example Request Body (Full Update):
Response (200 OK)
Returns the updated user object with all current field values.
Response Fields
User Object (item)
uuid
string
Unique user identifier.
user_abc123def
username
string
User's login name.
john.smith
status
string
Current user status.
ACCEPT
is2fa
boolean
2FA enabled status.
true
createAt
string
Original creation timestamp.
2024-01-15T10:30:00Z
updateAt
string
Last update timestamp.
2024-03-20T14:22:00Z
name
string
User's full name.
John Smith
comment
string
Administrative comments.
Account upgraded to premium
Example Response:
Examples
Update User Status (cURL)
Update Password and Personal Info
Complete User Profile Update
Error Responses
User Not Found:
Invalid Status:
Password Complexity Error:
Unauthorized:
Customer Not Found:
Notes
Update Behavior
Partial update - only included fields are modified
updateAttimestamp is automatically updatedSome status transitions may have business logic restrictions
Password changes may require additional verification
Password Requirements
Minimum length (typically 8-12 characters)
Requires uppercase and lowercase letters
Requires numbers and/or special characters
Cannot contain username or common patterns
Best Practices
Use partial updates to avoid overwriting unchanged fields
Validate status transitions according to business rules
Consider user notification for password changes
Use comments to document reasons for changes
Common Use Cases:
User account moderation and approval
Password reset operations
User profile information updates
Account status management (activation/deactivation)
2FA enrollment management
Status Transition Rules:
Some status changes may require additional verification
Certain statuses may be irreversible
Business rules may restrict certain transitions
Security Considerations:
Password changes should trigger session invalidation
Status changes to
BANNEDorREJECTEDmay restrict access immediately2FA enrollment may require user confirmation
Request sample
Response sample
Last updated

