---
title: "Get a custom parameter"
type: reference
method: GET
path: /rest-api/custom-parameters/{parameterId}.do
tag: "Custom Parameters"
---

# Get a custom parameter

`GET https://YOUR-NETWORK-DOMAIN/rest-api/custom-parameters/{parameterId}.do`

One parameter by its id or its name, with the Custom Parameter targeting rules on live entities that read it. A rule's neverMatches is true when one of its One of values holds the parameter's list separator, so no single item of a split request value can equal it. Rules and the description come back only to callers with the CUSTOM_PARAMETERS admin permission: rules name other clients' entities and targeting values, and the description is the admins' own note. Fields: id, name (without the cp. prefix), label, description, valueMode (DYNAMIC: any value; STATIC: one of values), allowOtherValues, values ([{value, label}] in list order), listSeparator (COMMA, PIPE, SEMICOLON, WHITESPACE, their ids 1 to 4, or null: the character a request value carrying several values is split on before a One of rule matches it item by item), recordInAnalytics, builtIn (seeded with the platform: kept by name, never deleted), canBeRemoved, createdAt, updatedAt.

## Path params

| Name | Type | Required | Example | Description |
|---|---|---|---|---|
| `parameterId` | string | yes | `genre` | Parameter id or name |

## Responses

- `200` — {parameter, rules (CUSTOM_PARAMETERS admins only): [{targetId, rule, kind, parameter, operation, values, text, ownerType, ownerId, ownerName, advertiserId, campaignId, siteId, zoneId, neverMatches}]}
- `400` — Bad request — invalid or missing parameters
- `401` — Authentication error
- `403` — Forbidden — insufficient permissions
- `404` — No parameter with this id or name

## Example request

```bash
curl --request GET \
  --url 'https://YOUR-NETWORK-DOMAIN/rest-api/custom-parameters/genre.do' \
  --header 'X-Api-Key: YOUR_API_KEY'
```

Source: https://epom.com/ad-server/docs/api/custom-parameters/get-custom-parameters-by-parameter-id