This article describes the DSP Traffic API and core traffic objects and their relationships.
Overview
The Yahoo DSP enables you to programmatically monitor, create, and manage advertising campaigns via resources that are exposed through the DSP Traffic API.
Yahoo DSP developers and partners can use these resources to manage advertisers, campaigns, lines, audiences, creatives, and more.
A resource is an object exposed through an endpoint. Resources are generally defined by multiple properties. These properties may be defined as integers, strings, arrays, or objects.
Endpoints
The Yahoo DSP API trafficking endpoint accepts requests for creating, updating and retrieving campaign related elements.
https://dspapi.admanagerplus.yahoo.com/traffic/Public Names of Resources
The public names used for Yahoo DSP traffic objects is sometimes different than the name used for these objects in the DSP Traffic API.
Throughout the DSP Traffic API documentation the name of the resource is preferred over the public name. For example, the term beacon is used instead of the term pixel, which is used in the Yahoo DSP console.
The table maps the public name to the resource endpoint.
Public Name | Resource Endpoint |
|---|---|
Seat |
|
Advertiser Group |
|
Advertiser |
|
Campaign |
|
Composite Audience |
|
Conversion Rule Audience |
|
Device ID Audience |
|
Email / Phone Number Audience |
|
Lookalike Audience |
|
Mail Domain Audience |
|
Mail Event Audience |
|
Point of Interest Audience |
|
Search Keyword Audience |
|
Pixel |
|
Contextual |
|
Site Lists and App Lists |
|
User Group |
|
Exchange |
|
Deal |
|
Creative |
|
Ad |
|
Line |
|
Bid Multiplier |
|
Targeting |
|