Latest revision as of 18:19, 27 July 2018

• 5.19 • 5.2 • 5.3 • 5.8

Expected Parameters

This returns an array of expected parameters. The parameters are optional. They may be used, for example, to look for the most qualified agents to handle the requested chat sessions and/or to display user information for the agents. These parameters are initially specified for the Messaging/Chat scenario entry through which this mobile application will communicate with the contact center.

Currently, the following parameter types are supported:

PHONE
TEXT
EMAIL
FIRST_NAME
LAST_NAME
ACCOUNT
COMPANY

URL

http[s]://<host>:<port>/clientweb/api/v1/parameters?tenantUrl=<tenantUrl>

Method

GET

Returns

200 – Names and types of parameters that may be expected from the client application (content type: application/json)

Example

{

"parameters":[

{
"<name>":”<type>”
},
...

]

}

Errors

401 – Unauthorized

< Previous | Next >< Previous | Next >

@@ Line 1: / Line 1: @@
 <translate>= Expected Parameters=
-This returns an array of expected parameters. The parameters are optional. They may be used, for example, to look for the most qualified agents to handle the requested chat sessions and/or to display user information for the agents. These parameters are initially specified for the [[contact-center-administrator-guide/MobileandWeb|Mobile/Web scenario entry]] through which this mobile application will communicate with the contact center.
+This returns an array of expected parameters. The parameters are optional. They may be used, for example, to look for the most qualified agents to handle the requested chat sessions and/or to display user information for the agents. These parameters are initially specified for the [[contact-center-administrator-guide/Messaging|Messaging/Chat scenario entry]] through which this mobile application will communicate with the contact center.
 Currently, the following parameter types are supported:

Navigation menu