# getContactDetails
Description: get detailed information about the user.
The result will come as a notification detailsInfo.
Request example:
{
"method" : "getContactDetails",
"requestId" : "1",
"peerId" : "user1@some.server"
}
Response example:
{
"method" : "getContactDetails",
"requestId" : "1",
"result" : true
}
If peerId
is changed (converted as shown below), the response will contain an additional parameter callId
.
Response example:
{
"method" : "getContactDetails",
"requestId" : "1",
"callId" : "user10@some.server",
"result" : true
}
Parameter description:
peerId
- unique user identifier (TrueConf ID). Application:PeerId - supported. It's automatically converted to CallId inside the application and the command is executed with it.
CallId - supported
InstanceId - is supported. Inside the application, it is automatically converted to CallId and the command is then executed with it.
requestId
- unique request identifier. More details can be found herecallId
- unique identifier of the user after conversion
See also: