---
title: "Get advertiser by ID"
type: reference
method: GET
path: /rest-api/advertisers/{advertiserId}.do
tag: "Advertisers"
---

# Get advertiser by ID

`GET https://YOUR-NETWORK-DOMAIN/rest-api/advertisers/{advertiserId}.do`

Returns the full details of a single advertiser including name, active status, contact name, contact email, description, creation date, advertising categories, and selfServeCpmFloorAdjustment. The authenticated user must have VIEW permission on CAMPAIGNS at either ALL or SHARED level; if SHARED, a share of any type must exist between the requester and the advertiser. Returns a JSON object with fields: id, name, active, contactName, contactEmail, description, created (with timeStamp, format, value), category, and selfServeCpmFloorAdjustment. With the MANAGE_COMPLETENESS_DELAY_INVENTORY permission it also carries the data-completeness settings the console shows: confirmationDelay, preliminaryConfirmationDays and lastConfirmedDate (yyyy-MM-dd, null when not set) — the values /advertisers/update takes. The response also carries additionalFieldValues: every custom field the network defines for this entity type, keyed by field id, each with its name and this entity's value (null when unset) - the values of /rest-api/additional-fields/{entityType}/{entityId}.

## Path params

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

## Responses

- `200` — Advertiser details
- `400` — Bad request — invalid or missing parameters
- `401` — Unauthorized — authentication failed or missing credentials
- `403` — Insufficient permissions
- `404` — Advertiser not found or deleted

## Example request

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

Source: https://epom.com/ad-server/docs/api/advertisers/get-advertisers-by-advertiser-id