Package-level declarations
Nimbus implementation of the OpenRTB 2.5 Spec.
Types
This object should be included if the ad supported content is a non-browser application (typically in mobile) as opposed to a website. A bid request must not contain both an App and a Site object. At a minimum, it is useful to provide an App ID or bundle, but this is not strictly required.
This object represents a native asset object, which is the main container for each asset requested or supported by Exchange on behalf of the rendering client.
The top-level bid request object contains a globally unique bid request or auction ID.
The data and segment objects together allow additional data about the related object (e.g., user, content) to be specified. This data may be from multiple sources whether from the exchange itself or third parties as specified by the id field. A bid request can mix data objects from multiple providers. The specific data providers in use should be published by the exchange a priori to its bidders.
This object provides information pertaining to the device through which the user is interacting.
This object encapsulates various methods for specifying a geographic location.
This object describes an ad placement or impression being auctioned.
Enum representing the user Gender to be sent to Nimbus
This object contains any legal, governmental, or industry regulations that apply to the request.
This object describes the nature and behavior of the entity that is the source of the bid request upstream from the exchange.
This object contains information known or derived about the human user of the device (i.e., the audience for advertising).
This object represents an in-stream video impression.