The new docs.trellix.com offers a modernized UI and AI-powered features like conversational searches. Content is currently available only in English. Other languages will be available in mid-October 2026. We hope you enjoy the new experience.

REST API Interface

Prev Next

A high-level overview of the API provided by the IOC Streaming module is listed in the following table. This API provides the ability to add/modify/remove indicators and conditions that are published to your endpoints, according to your detection needs. The pre-configured ,Trellix rules can be disabled/enabled at the indicator level. You have the full capability to customize the rules you created.

Theme

Detail

Verb / Operation

health

Return the health of this endpoint server module

GET /v1/health

Get the total bytes sent to Helix for the current interval

GET /v1/health/statistics

content

Retrieve the details for the published version of content

GET /v1/content

Publish a new version of content

POST /v1/content

conditions

Return a list of streaming conditions

GET /v1/conditions

Return a specific condition

GET /v1/conditions/{condition}

Update a specific condition

PUT /v1/conditions/{condition}

Remove a specific condition

DELETE /v1/conditions/{condition}

indicators

Return a list of streaming indicators

GET /v1/indicators

Create one or more indicators

POST /v1/indicators

Return a specific indicator

GET /v1/indicators/{indicator}

Update a specific indicator

PUT /v1/indicators/{indicator}

Remove a specific indicator

DELETE /v1/indicators/{indicator}

Disable a specific indicator

POST /v1/indicators/{indicator}/disable

Enable a specific indicator

POST /v1/indicators/{indicator}/enable

Intel

Return information about the latest DTI package applied

GET /v1/content/sc

The typical lifecycle operations are as follows:

Create: For a new set of conditions to collect under an indicator you must:

  1. Create a new indicator using POST /v1/indicators, setting the enabled state to false. This will return an ID for the new indicator in the response

  2. Create the one or more conditions that align under this indicator using POST

/v1/indicators/{ID}/conditions. Note that an ID will be returned in the response for each condition that you create. This ID we will denote as IDc, below.

  1. Update the indicator, setting the enabled state to true using POST /v1/indicators/{ID}/enable. This will make the new indicator available to your endpoints.

Change: To modify the metadata:

  1. For an indicator, use PUT /v1/indicators/{ID}

  2. For a condition, use PUT /v1/condition/{IDc}

  3. To add another condition to an existing indicator, use POST /v1/indicators/{ID}/conditions

  4. To remove a condition that is associated to an indicator, use DELETE /v1/indicators/{ID}/conditions/{IDc}. Once the association is removed, mark it for deletion/cleanup using DELETE /v1/conditions/{IDc}

Remove: To remove an indicator and its associated conditions

  1. Update the indicator setting the enabled state to false using POST /v1/indicators/{ID}/disable

  2. List the conditions attached to the indicator using GET / v1/indicators/{ID}/conditions

  3. For each condition that exists in the list of the response, remove it using step (4) under the Change- section.

  4. Remove the indicator using DELETE /v1/indicators/{ID}

The operations discussed affect the indicators and conditions that is published to your endpoints. The IOC Streaming Server module will pick up these changes and publish the updated content automatically. If you prefer to have finer grained control over the publication, either to publish on demand, or to control the version ID assigned to the published content, use the POST /v1/content operation.

The most up to date documentation of the API is available via the API Documentation module on the Endpoint Security Server. This module provides documentation for all the API available on the Endpoint Security Server, including the IOC Streaming module. It uses the Swagger/OpenAPI format to explain the parameters and data models that are used to interact with this module.

Rest_API_Interface.png