--- title: "Get Activity Feed configuration" slug: "get-activity-feed-configuration" tags: ["EDR with Forensics (EDRF)", "Endpoint Security"] updated: 2026-08-26T19:31:02Z published: 2026-08-26T19:31:02Z canonical: "docs.trellix.com/get-activity-feed-configuration" --- > ## 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. # Get Activity Feed configuration ### Overview This endpoint retrieves a complete list of all active activity feed configurations. The response is an array of configuration objects, each detailing an event topic and its configured destination (S3, Syslog, or Webhook). Use this API to review and audit your current data streaming setups. It's the primary method to programmatically verify which data feeds are active before attempting to create a new one, or to identify a specific configuration's ID for modification or deletion. This API provides a centralized, programmatic view of all Trellix data export rules, enabling automated configuration management and validation. ### Authentication Authentication type: Bearer Token, API Key. You can create a token using client credentials obtained through the [developer portal](https://developer.manage.trellix.com/). The API Key (`x-api-key`) is provided in your onboarding email or on the API Access Management page. ### Path *(or URL)* ``` GET https://{Trellix EDR_gateway_URL}/edr/v2/activity-feed/configurations ``` ### Request ###### Request headers ``` Authorization: Bearer Content-Type: application/vnd.api+json x-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](https://developer.manage.trellix.com/public) page. ###### Request parameters No request parameters. ### Response ###### Response example ``` {  "jsonapi": {    "version": "1.0"  },  "meta": {    "totalResourceCount": 10  },  "data": [    {      "id": "ce5cdfff-7818-455a-bc60-841be3513f4a",      "type": "activityFeed",      "attributes": {        "topic": "threatEvents",        "clientEmailId": "example@gmail.com",        "configType": "s3Config",        "enableCompressedOutput": "true",        "s3Config": {          "s3Prefix": "/prefix",          "roleARN": "arn:aws:iam::91574147XXX:role/EAF_S3CrossAccountAccess",          "s3BucketName": "example-bucket",          "awsRegion": "us-west-2"        }      }    }  ] } ``` ### Response codes | Status | Response | Description | | --- | --- | --- | | 200 | OK | Your request was processed successfully. The server has returned the requested data. | | 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. |