Also see: Triton Digital API Use Agreement
General Considerations for all APIs
If some of these APIs return an error message, the API integrator’s platform needs to both log it and show it to the end user.
Admin Bidconf API
Requires: Login API
Documentation available in https://yield-op.api.tritondigital.com/admin/doc/openapi
Manage demand partners, ad partners, and other programmatic advertising objects. This is the same API that the TAP Programmatic user interface uses.
Booking API
Requires: Login API
Documentation available in https://tap-api.tritondigital.com/docs
Manage advertisers, campaigns and users in TAP. Also, get some basic delivery metrics from TAP. Delivery metrics returned by the Booking API are virtually real-time.
DMP Admin API
Requires: Login API
Documentation available in https://dmpadmin.tritondigital.com/docs
Get the audience segments that can be used by the client as targeting rules in TAP.
Hierarchy API
Requires: Login API
Documentation available in http://tritonsecurity.tritondigital.com/v2/docs
Get a publisher’s groups, markets, and stations.
A station is the main targeting and reporting unit in Triton’s platform. Groups and markets are different grouping entities. The Hierarchy API can return either stations, markets and groups separately, or the full hierarchy.
When getting the stations that can be targeted from TAP, we recommend using the tap_only query parameter.
Inventory Forecasting API
Requires: Login API
Documentation available in https://avails.tritondigital.com/docs
Forecast the available advertising inventory for certain time, audience, and content criteria.
We recommend letting the end user enter as much information as possible about the campaign so that the forecast is as accurate as possible.
Login API
Documentation available in https://login.tritondigital.com/docs
Use the Authentication endpoint to get a token to use it in subsequent requests.
The API Integrator needs to check the token’s expiration date in its payload. When it has expired, get a new token.
Metrics API
Requires: Login API
Documentation available in https://metrics-api.tritondigital.com/docs/#/
Get reports from the different Triton Explore tools.
For information on when partial, reliable, and final numbers are available, as well as the time zone on which each report is based, see Expected Data Delays.
Recommendations:
The Metrics API is only available to customers who purchased the corresponding product. Therefore we recommend you implement any other API independently from the Metrics API (i.e. without relying on calling the Metrics API).
Metrics API licenses include a limited number of monthly queries. We recommend the API integrator works with the common client to not exceed the number of allowed queries.
The API integrator should consider the limitation in the number of results outlined in the documentation and use filters in order to build queries that don’t exceed the maximum number of results.
TAP Explore’s Impressions reports include flights using any pricing method, while Spots reports only include flights using CPS pricing method. As a consequence, CPS flights will show up in both reports. It’s important to bear in mind that CPS flights deliver spots; the impressions shown for those flights in the Impressions report are a calculation.
Starship API
Requires: Login API
Documentation available in https://starship.api.tritondigital.com/swagger-ui/index.html#/
Get the contextual tags that can be used by the client as targeting rules in TAP.
Station Tags API
Requires: Login API
Documentation available in https://tag-api.api.tritondigital.com/docs
Get the station tags that can be used by the client as targeting rules in TAP. Station tags are a non-hierarchical method of grouping stations.