--- title: "Creating an HTTP Event Collector Token on a Splunk Enterprise Server" slug: "creating-an-http-event-collector-token-on-a-splunk-enterprise-server" tags: ["Product Usage", "EX 11.x", "FX 11.x", "AX 11.x", "NX 11.x", "Network Security"] updated: 2026-09-12T20:42:40Z published: 2026-09-12T20:42:40Z canonical: "docs.trellix.com/creating-an-http-event-collector-token-on-a-splunk-enterprise-server" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Creating an HTTP Event Collector Token on a Splunk Enterprise Server Log into the Splunk Enterprise server using the Web UI and create an HTTP Event Collection (HEC) token to connect and run the Layer 7 Metadata Event Exporter feature on your ADD Product Series appliance. An HEC token is a 32-bit number that allows a logging connection between agents and HTTP clients, such as the ADD Product Series appliance and Splunk Enterprise. After the token is presented and accepted, events can be delivered by your ADD Product Series appliance in JSON format to the Splunk Enterprise server. > [!NOTE] > Note > > You disable per-token acknowledgments by clearing the **Enable indexer acknowledgement** checkbox. ### Prerequisites - Administrator or Operator access to the ADD Product Series appliance. - An active subscription to the Splunk Enterprise server. - A connection to the Splunk Enterprise server. **To create the Splunk HEC Token:** 1. Log into the Splunk Enterprise server Web UI. 2. Click **Settings** > **Data Inputs**. The HTTP Event Collector page appears. 3. Click **New Token**. ![NX_SplunkCreateToken_scap.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-d1ec0867-4357-88ce-f7be-d136a28a605c.png?sv=2026-02-06&spr=https&st=2026-11-20T04%3A17%3A34Z&se=2026-11-20T05%3A17%3A34Z&sr=c&sp=r&sig=aTTf79N1BU%2FsaVy8Ijhf4xGT9ws9fRfldxCal%2FK0iP4%3D) The Add Data page appears. 4. Click **Next** to configure a new token for receiving data over HTTP. ![NX_SplunkConfigureToken_scap.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-43b33d2d-a702-4ba5-b850-67884307d0f9.png?sv=2026-02-06&spr=https&st=2026-11-20T04%3A17%3A34Z&se=2026-11-20T05%3A17%3A34Z&sr=c&sp=r&sig=aTTf79N1BU%2FsaVy8Ijhf4xGT9ws9fRfldxCal%2FK0iP4%3D) Enter the token information as indicated in the following table. | Field | **Description** | | --- | --- | | Name | A name for the HEC input token. | | Source name override | A name for the event data associated with the HEC token. | | Description (optional) | A description for the HEC input token. | | Output Group (optional) | The name of an existing output forwarding group set up by the Splunk administrator. | | Enable indexer acknowledgement | Clear the checkbox. | 5. Click **Next**. 6. Click **Select** and then select **Structured** from the **Select Source Type** pull-down menu to format and categorize your data. 7. Choose **json_no_timestamp** format for event data. 8. Click **Review** to verify your HEC token input settings. 9. Click **Submit** to confirm settings. 10. Copy and save the token value for your reference.