From Bright Pattern Documentation
|
|
Line 1: |
Line 1: |
− | <translate>= Expected Parameters=
| + | #REDIRECT [[Api]] |
− | 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:
| |
− | * 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 ===
| |
− | {|border="1" style="border-collapse:collapse" cellpadding="5"
| |
− | |''{''
| |
− | | |
− | ''"parameters":[''
| |
− | | |
− | <blockquote>''{''
| |
− | | |
− | ''"<name>":”<type>”''
| |
− | | |
− | ''},''
| |
− | | |
− | ''...''
| |
− | </blockquote>
| |
− | '']''
| |
− | | |
− | ''}''
| |
− | |}
| |
− | | |
− | == Errors ==
| |
− | 401 – Unauthorized
| |
− | | |
− | | |
− | | |
− | <center>[[mobile-web-api-specification/CheckAvailability|< Previous]] | [[mobile-web-api-specification/RequestChat|Next >]]</center>
| |
− | </translate>
| |
Latest revision as of 22:57, 6 August 2020