---
title: "Create advertiser protocol targeting"
type: reference
method: POST
path: /rest-api/advertiser/{advertiserId}/targeting/protocol/create.do
tag: "Targeting Rules"
---

# Create advertiser protocol targeting

`POST https://YOUR-NETWORK-DOMAIN/rest-api/advertiser/{advertiserId}/targeting/protocol/create.do`

Creates a protocol targeting rule for the specified advertiser. The rule filters ad requests based on the HTTP protocol used by the page. Available values are HTTP and HTTPS. This is useful for ensuring ads are served only over secure connections. Requires UPDATE permission on the advertiser and MANAGE_DEMAND_TARGETING user permission.

## Path params

| Name | Type | Required | Example | Description |
|---|---|---|---|---|
| `advertiserId` | integer | yes | `1234` | Unique numeric ID of the advertiser |

## Form params

| Name | Type | Required | Example | Description |
|---|---|---|---|---|
| `rule` | string | yes | `INCLUDE` | Targeting rule type — INCLUDE for whitelist or EXCLUDE for blacklist |
| `protocol` | string | yes | `HTTPS` | Protocol to target — HTTP or HTTPS |

## Responses

- `200` — Success
- `400` — Invalid targeting value
- `401` — Unauthorized
- `403` — Forbidden
- `404` — Advertiser not found
- `500` — Internal server error

## Example request

```bash
curl --request POST \
  --url 'https://YOUR-NETWORK-DOMAIN/rest-api/advertiser/1234/targeting/protocol/create.do' \
  --header 'X-Api-Key: YOUR_API_KEY' \
  --header 'Content-Type: application/x-www-form-urlencoded' \
  --data-urlencode 'rule=INCLUDE' \
  --data-urlencode 'protocol=HTTPS'
```

Source: https://epom.com/ad-server/docs/api/targeting-rules/post-advertiser-targeting-protocol-create