---
title: "Get advertiser limits"
type: reference
method: GET
path: /rest-api/advertiser/{advertiserId}/limits.do
tag: "Limits"
---

# Get advertiser limits

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

Retrieves the current impression, click, conversion, budget and opportunity limits configured for the specified advertiser. The response includes every cap the set/update endpoints accept, with its current counter — daily, weekly, monthly and total — the date range (startDate/endDate, GMT+0), evenPacing, useLocalTime and limitsSet=true. An advertiser without limits answers {advertiserId, limitsSet:false}. Requires UPDATE permission on the advertiser and the MANAGE_CAPPING_AND_LIMITATIONS user permission. Each cap and counter (budget, opportunities, impressions, clicks, conversions — every period) is shown only when the role holds its limit permission (e.g. WEEKLY_CLICKS_LIMIT, MONTHLY_BUDGET) enabled or readonly, like the console Limits card.

## Path params

| Name | Type | Required | Example | Description |
|---|---|---|---|---|
| `advertiserId` | integer | yes | `1001` | Unique numeric identifier of the advertiser whose limits should be retrieved |

## Query params

| Name | Type | Required | Example | Description |
|---|---|---|---|---|
| `timezoneOffset` | integer | no | `120` | The caller's offset from UTC in minutes (east positive). With the limit on local time, startDate/endDate are answered in that offset, as the console shows them; omitted, they are in UTC |

## Responses

- `200` — Advertiser limits, or {advertiserId, limitsSet:false} when none are set
- `400` — Bad request — invalid or missing parameters
- `401` — Authentication error
- `403` — Not enough permissions
- `404` — Advertiser not found

## Example request

```bash
curl --request GET \
  --url 'https://YOUR-NETWORK-DOMAIN/rest-api/advertiser/1001/limits.do?timezoneOffset=120' \
  --header 'X-Api-Key: YOUR_API_KEY'
```

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