Welcome
Administration
Learn about how to configure, manage, and maintain HCL Detect environments. It includes details on system setup, user management, and permissions, ensuring seamless operation and efficient deployment of your continuous delivery processes.
Destination Management
Use CLI commands to configure, validate, and manage destination endpoints for Detect event delivery.
API (HTTP REST) Connector for Destinations
Send detected events to an external system over HTTP by configuring an API (HTTP REST) connector on a destination.
API Connector Security Considerations and Limitations

Getting Started
Welcome to the documentation for HCL Detect, where you can find information about how to install, maintain, and use this service.
Installation
Learn more about HCL Detect installation and deploying core components of the product.
Administration
Learn about how to configure, manage, and maintain HCL Detect environments. It includes details on system setup, user management, and permissions, ensuring seamless operation and efficient deployment of your continuous delivery processes.
- Introduction
  Use this guide to administer HCL Detect, including user and role access, CLI-based configuration and management tasks, DEL reference topics, and support resources.
- User & Role Management
  This page explains how to manage roles and permission in HCL Detect.
- Configuration Management
  Use CLI commands to query and validate the infrastructure settings required for Detect operations.
- Metadata Management
  Use CLI commands to discover data sources, search tables, and retrieve column metadata for Detect integrations.
- Profile Management
  Manage profile definitions and attributes through the HCL Detect UI or CLI.
- Feed Application
  Create and manage feed applications through the HCL Detect UI or CLI.
- About derived attribute functions
  Derived attribute functions enable you to offload complex calculations involving multiple tuple attributes to custom Python scripts.
- Feed Parser Mapping
  Use CLI commands to define and maintain feed parser mappings between incoming feed fields and Detect target attributes.
- Destination Management
  Use CLI commands to configure, validate, and manage destination endpoints for Detect event delivery.
  - What is a Destination?
  - Available Commands
  - API (HTTP REST) Connector for Destinations
    Send detected events to an external system over HTTP by configuring an API (HTTP REST) connector on a destination.
  - Best Practices
    Recommendations for naming and validating destinations.
  - Complete Example: End-to-End Destination Setup
  - Sample JSON Payloads Reference
  - FAQ
  - Appendix: Field Reference
- Crypto Management
  Use CLI crypto utilities to encrypt and decrypt sensitive values used in Detect configuration workflows.
- Troubleshooting & Common Errors
- Detect Expression Language
- Detect Expression Language Built-in Functions
Working with the System
The section provides comprehensive instructions for creating, configuring, and managing marketing events. It covers topics such as defining audience conditions, setting up triggers, deploying events, and tracking their performance. Additionally, this section includes explanations of key terminology and offers advanced options to optimize event management.
System Data Model
This section provides detailed information about the internal tables used within the Detect module. It includes descriptions of each table's structure, purpose, and relationships, aiding administrators and developers in understanding and managing the underlying database schema effectively.

API Connector Security Considerations and Limitations

Security considerations

Use HTTPS target endpoints wherever possible.
Keep credentials only in the Platform API configuration. Do not place credentials in destination headers or in the JSON payload template.
Import self-signed or internal CA certificates into Java truststore.
Rotate client secrets and passwords periodically, and update the Platform API configuration whenever you do.
Restrict access to the Platform configuration area where API connector credentials are stored.

Limitations

Only JSON payloads are supported.
Only HTTP POST is supported for publishing events.
Only three authorization types are supported: no authorization, basic authentication, and bearer token with client ID and client secret. API keys and other OAuth flows are not supported.
Each event is sent as an individual HTTP request rather than in a batch, so high-volume destinations may encounter the downstream API's own rate limits (HTTP 429).