2.8 Change Participant Information
Brief description：
Change Participant Information
Request URL：
-https://telopenapi.quanshi.com/tel-conference/deal/v1/conference/updateParty
Request method：
POST
Request Parameter：
| Parameter Name | Required | Type | Description |
|---|---|---|---|
| confId | Yes | Int | G-Net Meeting id |
| userId | Yes | Int | G-Net user Id |
| custId | Yes | Int | Participant id |
| name | Yes | String | Participant name |
| phone | Yes | String | Participant phone number |
| role | Yes | String | Role (0 Consultant, 1 Consulting Client) |
| country | Yes | String | Country code |
| area | Yes | String | Area code, fill in null character string if no code |
| partyId | No | String | PartyId in acm |
Request parameter example
{
"confId": 13679 ,
"userId": 6135684 ,
"custId": 1323 ,
"name":"",
"phone":"13211222122",
"role":"0",
"country":"86",
"area":"",
"partyId":""
}
Curl Request:
curl -l -H "Content-type:application/json" -X POST -d '{"userId":2258811, "confId":833045, "custId": 8416427, "name":"jack","phone":"18100000000","role":"1","country":"86","area":"","partyId":"1658301720850YY10000"}' -k --cert /d/cer/qs.deal.20220715/qs.deal.client_cert.pem --key /d/cer/qs.deal.20220715/qs.deal.client_key.pem https://telopenapi.quanshi.com/tel-conference/deal/v1/conference/updateParty
Return parameter description:
| Parameter Name | Type | Description |
|---|---|---|
| code | Int | Response Status value |
| msg | String | Error description |
| requestId | String | Request id, G-Net use this parameter to trace the request |
Response example
{
"code": 0 ,
"msg":"Operation_Succeeded"
"requestId" : "7bf63bab-5a00-fd0d-9d23-5cd102932b5a"
}
