Delete all Activity feed configurations for a tenant

Prev Next

Overview

This endpoint permanently deletes an activity feed configuration, which stops the associated data stream. Target the configuration by its configuration-id in the path. The action is irreversible and a successful response returns 204 No Content. Use this API to decommission a data feed. This is necessary when the external system receiving the data is retired, or when you are replacing an existing data pipeline and need to remove the old configuration. This API provides a clean method for programmatically managing data export rules, ensuring that sensitive security data is only sent to currently approved and active destinations.

Authentication

Authentication type: Bearer Token, API Key.

You can create a token using client credentials obtained through the developer portal. The API Key (x-api-key) is provided in your onboarding email or on the API Access Management page.

Path (or URL)

<HTTPS Method>
DELETE https://{Trellix EDR_gateway_URL}/edr/v2/activity-feed/configurations

Request

Request headers
Authorization: Bearer <your_bearer_token>
Content-Type: application/vnd.api+json
x-api-key: <your_api_key>
  • Authorization: This header is used to authenticate your request. You need to replace <your_bearer_token> with the actual token you generate.

  • Content-Type: This header tells the server that the request body format is json:api. Even though this specific call has no request body, the API requires this header.

  • x-api-key: This is a custom header required by the Trellix API for authentication. You'll need to replace <your_api_key> with the key from your onboarding email or the API Access Management page.

Request parameters

Parameters

Data type/Values

Description

configurationId

string

This is a path parameter. A unique identifier for the configuration.

Response codes

Status

Response

Description

204

No Content

The configuration was permanently deleted.

400

Bad request

The server couldn't understand your request, likely due to a syntax error or an invalid parameter.

401

Access denied request

Your request was rejected because it lacks valid authentication credentials. Check your API key and token.

403

Forbidden

You are not authorized to access this resource. While your credentials may be valid, you don't have the necessary permissions.

404

Not Found

The specific resource or endpoint you requested does not exist.

415

Unsupported Media Type

The server rejected your request because the data format (Content-Type) is not supported.

429

Too Many Requests

You've exceeded the rate limit by sending too many requests in a short period. The Retry-After header in the response will tell you how long to wait before trying again.

500

Internal Server Error

Something went wrong on the server's end. This is not an issue with your request.