McDewey

C H A P T E R 4 Cisco Finesse Configuration APIs Administrators use the Cisco Finesse configuration APIs to configure the following: • System, cluster, and database settings • Finesse desktop and call variable layout • Reason codes and wrap-up reasons • Phonebooks and contacts • Team resources • Workflows and workflow actions Finesse configuration APIs require administrator credentials (the application user ID and password) to be passed in the basic authorization header. If a user repeatedly passes an invalid password in the basic authorization header to a configuration API, on the fifth invalid attempt, Finesse blocks the user's access to all configuration APIs for 5 minutes. This lock period differs from the 30-minute lock period implemented for the Finesse administrator console. Note In a stand-alone Finesse deployment with Unified CCE, you cannot run configuration APIs against the secondary Finesse server. If you attempt to run a ReasonCode API against the secondary Finesse server, Finesse responds with a 403 “Forbidden” error. In a coresident Finesse deployment with Unified CCX, administration on the secondary node is read-only. You can run a GET request against the secondary node. However, other requests (PUT, POST, or DELETE) result in a 403 “Forbidden” error. • SystemConfig, on page 206 • ConfigInfo, on page 210 • ECCVariableConfig, on page 212 • ClusterConfig, on page 214 • EnterpriseDatabaseConfig, on page 217 • LayoutConfig, on page 221 • ReasonCode, on page 236 • WrapUpReason, on page 244 • ChatConfig, on page 250 Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 205