---
title: "Read the network's ad server fees"
type: reference
method: GET
path: /rest-api/ad-server-fees.do
tag: "Ad Server Fees"
---

# Read the network's ad server fees

`GET https://YOUR-NETWORK-DOMAIN/rest-api/ad-server-fees.do`

What this network pays its ad server: the pricing type that decides how impressions are charged (SPLIT bills desktop, mobile and video separately, GLOBAL bills one rate for all of them, LEGACY is the old scheme), which plan the network is on, and every fee plan with its monthly price, the volumes it includes, the overage rates charged beyond them, the flexible per-impression prices, how header-bidding fills are charged and the AI assistant terms. This is the ad server's bill to the network, not what the network charges its own advertisers - those are the Network Finances operations. What each month came to is read with ad-server-fees/months.do, and what the AI assistant cost each user with ai-chat/usage.do. Requires the Ad Server Fees console permission (AD_SERVER_FEES or AD_SERVER_FEES_MANAGEMENT).

## Responses

- `200` — {success, pricingType, activePlanId, activePlanName, editable, defaultAiPriceMultiplier, plans:[...]}
- `400` — Bad request — invalid or missing parameters
- `401` — Authentication error
- `403` — The caller holds neither AD_SERVER_FEES nor AD_SERVER_FEES_MANAGEMENT

## Example request

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

Source: https://epom.com/ad-server/docs/api/ad-server-fees/get-ad-server-fees