---
title: "Read one DSP partner"
type: reference
method: GET
path: /rest-api/dsp-partners/{id}.do
tag: "DSP Partners"
---

# Read one DSP partner

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

One demand partner with every setting the list carries, and the three the list leaves out because they are read one partner at a time: the per-partner parameters its creatives then carry a field for, which sides and metrics its analytics are written to, and the connection parameters that pull them. Every setting the change operation accepts is answered here, so a change is confirmed by what was stored rather than by the call saying so. Requires the DSP Partners permission.

## Path params

| Name | Type | Required | Example | Description |
|---|---|---|---|---|
| `id` | integer | yes | `12` | The partner's id |

## Responses

- `200` — {success, editable, partner:{id, name, active, url, parameters, analyticsSync, ...}}
- `400` — Bad request — invalid or missing parameters
- `401` — Authentication error
- `403` — The caller does not hold the DSP Partners permission
- `404` — No partner with this id

## Example request

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

Source: https://epom.com/ad-server/docs/api/dsp-partners/get-dsp-partners-by--id