HCL TECHNOLOGIES ABOUT US PRODUCTS & SOLUTIONS RESOURCES CONTACT US

Home
HCL Interact Administrator's Guide
When you administer Interact you configure and maintain users and roles, data sources, and optional product features. You also monitor and maintain the design and runtime environments. Product-specific application programming interfaces (APIs) are available for you to use.
Understanding the Interact API
Interact serves offers dynamically to a wide variety of touchpoints. For example, you can configure the runtime environment and your touchpoint to send messages to your call center employees informing them of the best up sell or cross sell prospects for a customer who has called with a specific type of service inquiry. You can also configure the runtime environment and your touchpoint to provide tailored offers to a customer (visitor) who has entered a particular area of your Web site.
Designing the Interact API integration
Building your Interact API integration with your touchpoint requires some designing before you can begin implementation. You need to work with your marketing team to decide on where in your touchpoint you want the runtime environment to serve offers (define your interaction points) and what other kind of tracking or interactive functionality you want to use (define your events).
API Authentication
This feature provides you the option to enable authentication on Interact API calls. When it is enabled, Interact RT checks if an incoming API request has a valid authentication token, if not, it authenticates it using the supplied username and password with Marketing Platform. The request is rejected if the token is not valid and username / password is not valid. Each token has a non-extendable lifetime of the Interact session cache becomes timeout. The token is tied with the session-Id, which is provided during the startSession() API call. So all the other API calls validate this token before proceeding. This feature is disabled by default.

API Authentication

This feature provides you the option to enable authentication on Interact API calls. When it is enabled, Interact RT checks if an incoming API request has a valid authentication token, if not, it authenticates it using the supplied username and password with Marketing Platform. The request is rejected if the token is not valid and username / password is not valid. Each token has a non-extendable lifetime of the Interact session cache becomes timeout. The token is tied with the session-Id, which is provided during the startSession() API call. So all the other API calls validate this token before proceeding. This feature is disabled by default.