---
title: "List the logged custom parameter and cookie names"
type: reference
method: GET
path: /rest-api/analytics-configuration/request-filters.do
tag: "Analytics"
---

# List the logged custom parameter and cookie names

`GET https://YOUR-NETWORK-DOMAIN/rest-api/analytics-configuration/request-filters.do`

The names the raw-log writers keep or drop, by kind: CUSTOM_PARAMETER, the custom parameters carried by an ad request, and COOKIE_NAME, the cookies read from the visitor. Without 'type' both kinds are answered. Each kind's list is read one of two ways, and the answer says which under 'mode': INCLUDE, the default - only these names are logged - or EXCLUDE, where these are the names left out and everything else is logged. The switch is the *Blacklist* toggle on the console's Analytics configuration page (stored as the analyticsCustomParametersFilteringExclude / analyticsCookieNamesFilteringExclude network preference) and is not changed here, so read it before adding a name: in EXCLUDE mode a name you add stops being logged. While a kind's filtering is switched off in the ad-server configuration the list has no effect at all. Reading needs only an authenticated account.

## Query params

| Name | Type | Required | Example | Description |
|---|---|---|---|---|
| `type` | string | no | `CUSTOM_PARAMETER` | CUSTOM_PARAMETER or COOKIE_NAME; omitted answers both |

## Responses

- `200` — {success, filters: [{type, mode, total, names: [name]}]}
- `400` — 'type' names no filter kind
- `401` — Authentication error
- `403` — Forbidden — insufficient permissions

## Example request

```bash
curl --request GET \
  --url 'https://YOUR-NETWORK-DOMAIN/rest-api/analytics-configuration/request-filters.do?type=CUSTOM_PARAMETER' \
  --header 'X-Api-Key: YOUR_API_KEY'
```

Source: https://epom.com/ad-server/docs/api/analytics/get-analytics-configuration-request-filters