Device List Response Parameters
These parameters are included in the results when retrieving a list of devices via GET /agency/<dsp_agency_id>/dsp/device/.
| Parameter | Type | Description |
|---|---|---|
| id | int | Device ID |
| external_id | int | ID on the device owner's network |
| name | string | Device name |
| description | string | Device description |
| resolution | string | Format: <width>x<height> |
| orientation | int | 1 for landscape, 2 for portrait |
| is_deployed | bool | Indicates if the device is currently working |
| postal_code | string | Postal code |
| country | string | Two-letter ISO 3166-1 alpha-2 code |
| city | string | City |
| street | string | Street |
| floor | int | Floor |
| room | string | Room |
| latitude / longitude | float | Coordinates for map display |
| ad_plays_cost | object | Expanded format: cost per 1000 plays of a 1-second clip |
| cpm_cost | object | Expanded format: cost per 1000 potential contacts |
| cpv_cost | object | Expanded format: cost for 1 guaranteed view of a 1-second clip |
Here is a JSON example showing how those parameters appear in a real API response.
This typically comes from a GET request to the /api/v2/agency/<dsp_agency_id>/dsp/device/ endpoint. I have included the extended format data, which shows the localized costs for that specific screen.
Example: Device List Entry
{
"id": 1042,
"external_id": 550,
"name": "Central Station Main Hall - Screen A",
"description": "High-traffic digital totem located near the main information desk.",
"resolution": "1080x1920",
"orientation": 2,
"is_deployed": true,
"postal_code": "10117",
"country": "DE",
"city": "Berlin",
"street": "Europaplatz",
"building": "1",
"floor": 0,
"room": "Main Concourse",
"latitude": 52.525084,
"longitude": 13.369402,
"ad_plays_cost": {
"min": 120.50,
"max": 120.50
},
"cpm_cost": {
"min": 45.00,
"max": 45.00
},
"cpv_cost": {
"min": 5.25,
"max": 5.25
}
}Key Parameter Breakdown
Orientation (
2): According to the table,1is landscape and2is portrait. This tells your creative team to provide vertical assets.Location Granularity: Notice how the response provides not just
cityandstreet, but alsofloorandroom. This is vital for "Hyper-local" targeting (e.g., targeting only food courts or waiting areas).Cost Objects:
ad_plays_cost: The price for 1,000 displays of a 1-second clip on this specific screen.cpm_cost: The price for 1,000 potential contacts (audience reach).cpv_cost: The price for a single guaranteed view by your target demographic.
Status (
is_deployed): Atruevalue means the device is currently active and eligible to receive your ads.
Pro-Tip for Integration
If you are building a map-based UI for your customers, you would use the latitude and longitude fields from this response to plot the screen locations, and the resolution field to warn the user if their uploaded media won't fit that specific device.
Comments
0 comments
Please sign in to leave a comment.