Open RTB Bid Response Specifications
The response for a bid request will have the following structure:
Bid Response Object
Attribute | Required? | Description |
---|---|---|
id | Yes | ID of the bid request (string) |
seatbid | Yes | Collection of bids made by the bidder on behalf of a specific seat. |
seatbid
Attribute | Required? | Description |
---|---|---|
bid | Yes | ID of the impression object to which this bid applies (string) |
seatbid.bid
Attribute | Required? | Description |
---|---|---|
id | Yes | ID for the bid object chosen by the bidder (string) |
impid | Yes | ID of the impression object to which this bid applies (string) |
price | Yes | Bid price in CPM or CPC (float) |
adm | Yes | ExoClick XML/JSON Ad Markup (string) |
nurl | Yes | Win notification URL |
cid | No | Campaign ID to assist with ad quality checking (string) |
crid | Recommended | Creative ID to assist with ad quality checking (string) |
iurl | Recommended | URL of creative |
ext | No | ExoClick specific extension (object) |
Note:The nURL must be notified in order to ensure campaign capping and avoid getting the same response every time.
seatbid.bid.ext
Attribute | Required? | Description |
---|---|---|
btype | Recommended | Pricing Model. Values: 1 = CPM, 2 = CPC*. Default = 1 (int). Note: When response is for an Email Clicks zone request, 1 = Smart CPC. |
Note: Only Push Notification and Native ad formats may bid with the CPC pricing model.
Win Notification
When the parameter Bid Response Object > Seat Bid Object > Bid Object > nurl is in the bid response, a GET request must be performed to such URL.
Examples
You can find detailed examples of the Responses you can receive in the example page.