---
title: "Start a serving trace"
type: reference
method: POST
path: /rest-api/serving-traces/start.do
tag: "Banners"
---

# Start a serving trace

`POST https://YOUR-NETWORK-DOMAIN/rest-api/serving-traces/start.do`

For the next few minutes the ad servers record, for each ad request on the creative's linked placements this account may view, which creative was served and which were left out and why. Read the result with GET /rest-api/serving-traces/{traceId}. Recording starts within a minute. One trace runs per network at a time. Requires VIEW access to the creative's advertiser and to the placements' sites.

## Form params

| Name | Type | Required | Example | Description |
|---|---|---|---|---|
| `bannerId` | integer | yes | `3001` | The creative to trace |
| `minutes` | integer | no | `10` | How long to record, 1-15 minutes |

## Responses

- `200` — {success, traceId, bannerId, placementIds, startsAt, endsAt}
- `400` — minutes outside 1-15, no viewable linked placement, or another trace is running in the network
- `401` — Unauthorized — authentication failed or missing credentials
- `403` — No VIEW access to the creative
- `404` — Creative not found or deleted

## Example request

```bash
curl --request POST \
  --url 'https://YOUR-NETWORK-DOMAIN/rest-api/serving-traces/start.do' \
  --header 'X-Api-Key: YOUR_API_KEY' \
  --header 'Content-Type: application/x-www-form-urlencoded' \
  --data-urlencode 'bannerId=3001' \
  --data-urlencode 'minutes=10'
```

Source: https://epom.com/ad-server/docs/api/banners/post-serving-traces-start