---
title: "Read one scanned creative"
type: reference
method: GET
path: /rest-api/dsp-creative-scan/{id}.do
tag: "DSP Creative Scan"
---

# Read one scanned creative

`GET https://YOUR-NETWORK-DOMAIN/rest-api/dsp-creative-scan/{id}.do`

One creative's whole scan record: its verdict and the dates behind it, plus the three things the grid leaves out -- the markup that was submitted to the provider, exactly as it saw it; the flags it raised, which is what says whether a BLOCKED verdict is a true positive; and its raw answer and the context the creative was seen in. markupKind says how to read the markup: HTML for a creative, VAST for video XML, URL for a bare redirect. For an AUTO_APPROVED creative the markup is the untransformed original, because the reason it was let through is that it could not be transformed. Requires the DSP Creative Scan permission.

## Path params

| Name | Type | Required | Example | Description |
|---|---|---|---|---|
| `id` | integer | yes | `4821` | The scan record's id, as the list answers it |

## Responses

- `200` — {success, mayChangeScanProvider, creative:{id, status, skipReason, adMarkup, markupKind, flags, providerResponse, scanContext, ...}}
- `400` — Bad request — invalid or missing parameters
- `401` — Authentication error
- `403` — The caller does not hold the DSP Creative Scan permission
- `404` — No scan record with this id

## Example request

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

Source: https://epom.com/ad-server/docs/api/dsp-creative-scan/get-dsp-creative-scan