Update User

This feature helps to update the details of an existing user within the system. The Service URL of the module is given by the following link-

The domain can be: “app” or “ai”.

1. Code snippet for Web Service Use–

{

Headers

Every API call must include two-factor authentication by providing the following headers:

Authorization: Bearer <Generated_Token>
- The Bearer Token is generated upon a successful login.
X-API-KEY: <Your_Unique_API_Key>
- Note: This key is assigned by the QEval team. If not available, you can request it via email at Qeval@etechtexas.com

“empSrId”: “137799”,

“empId”: “John57”,

“firstName”: “John”,

“middleName”: “P”,

“lastName”: “Paul”,

“supervisorId”: “3332”,

“empType”: “FTE”,

“roleId”: 1,

“email”: “john.paul57@etechtexas.com”,

“campaignId”: 32506,

“locationID”: 2946,

“isSupervisor”: false,

“isAccessLocationBased”: false,

“isAccessIPBased”: false,

“partnerId”: 0,

“isPartnerAllowed”: false

“CampaignId”: 0,

“ClientId”: 1

}

2. Description for Request Parameters–

S.No	Name	Type	Description
1	empSrId	String	Employee Serial ID is automatically generated during user creation.
2	empId	String	ID of Employee
3	firstName	String	First name of the employee
4	middleName	String	Middle name of the employee
5	lastName	String	Last name of the employee
6	supervisorId	String	ID of Supervisor
7	empType	String	Type of employee
8	roleId	Int	Role ID of the employee
9	email	String	Email of user
10	campaignId	Int	ID of Campaign
11	locationID	Int	Location ID of user
12	isSupervisor	Bit	Is the user supervisor or not
13	isAccessLocationBased	Bit	Is the access location-based or not
14	isAccessIPBased	Bit	IP-based login restriction required or not
15	partnerId	Int	ID of partner
16	isPartnerAllowed	Bit	Is partner allowed or not
17	CampaignId	Int	ID of campaign
18	ClientId	Int	Client ID for tenant isolation

3. Response Example–

Success–

{

“Message”: “User updated successfully.”

}

Fail–

{

“Message”: “The request is invalid.”

}

API Documentation