Currently, curbing mobile money fraud in the country is nearly impossible. To tackle this issue, we propose developing a real-time database that allows users to query and determine if a phone number is likely fraudulent based on public contributions, especially from those who have experienced fraud.
Endpoint: /api/admin/users/update/{adminId}
Method: PUT
Description: Updates an existing admin's details. Password update is optional.
Authorization Required: Yes
Parameters:
Admin ID: The unique identifier for the admin.
First Name (optional): Admin's first name.
Last Name (optional): Admin's last name.
Email (optional): Admin's email address.
Phone Number (optional): Admin's phone number.
Password (optional): New password, if updating the password.
Permissions (optional): Updated permissions.
Validations:
Email Address:
Must be in a valid email format if provided.
Must be unique across the admin database if changed.
Password:
If provided, must meet complexity requirements.
Endpoint: /api/admin/users/update/{adminId} Method: PUT Description: Updates an existing admin's details. Password update is optional. Authorization Required: Yes
Parameters: Admin ID: The unique identifier for the admin. First Name (optional): Admin's first name. Last Name (optional): Admin's last name. Email (optional): Admin's email address. Phone Number (optional): Admin's phone number. Password (optional): New password, if updating the password. Permissions (optional): Updated permissions.
Validations: Email Address: Must be in a valid email format if provided. Must be unique across the admin database if changed. Password: If provided, must meet complexity requirements.
Feedback: Success: "Admin details updated successfully." Failure: "Failed to update admin details. Why ...."