> For the complete documentation index, see [llms.txt](https://docs.exoclick.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.exoclick.com/rtb/advertisers/open-rtb/adv-open-rtb-2.5-response.md).

# Open RTB 2.5 Bid Response

The response for a bid request will have the following structure:

## Bid Response Object

| Attribute | Required? | Description                                                         |
| --------- | --------- | ------------------------------------------------------------------- |
| id        | Yes       | ID of the bid request, must match id sent in the 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, must match id sent in the request (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       | Ad markup (string)                                                               |
| nurl      | Yes       | Win notification URL, it is recommended to use HTTP over HTTPS for nurl (string) |

### seatbid.bid.ext

| Attribute | Required?   | Description                                                                                                                       |
| --------- | ----------- | --------------------------------------------------------------------------------------------------------------------------------- |
| btype     | Recommended | Pricing Model. Values: 1 = CPM, 2 = CPC. Default = 1 (int). When the response is for an Email Clicks zone request, 1 = Smart CPC. |
|           |             | **Note**: Only Push Notification, Native ads, Direct Link, and Email Clicks may bid with the CPC pricing model.                   |

**Notes:**

* We support video in interstitial placements.
* The impid must match the one provided in the request.

### No Bid Response <a href="#no-bid-response" id="no-bid-response"></a>

To answer to a bid request without making an actual bid, an HTTP response code 204 "No Content" should be sent.

### Win and Billing Notification URLs <a href="#win-and-billing-notification-urls" id="win-and-billing-notification-urls"></a>

If either the **nURL** or the **bURL** are in the bid response and are valid URLs, ExoClick platform will send a GET request to them. These URLs can have a few tokens to be replaced by ExoClick before doing the GET:

```
${AUCTION_ID} - ID of the bid request; from "Bid Request Object -> id" attribute.
${AUCTION_BID_ID} - ID of the bid; from "Bid Response Object -> bidid" attribute.
${AUCTION_IMP_ID} - ID of the impression just won; from "Bid Request Object -> Impression Object -> id" attribute.
${AUCTION_SEAT_ID} - ID of the bidder seat for whom the bid was made; from "Bid Response Object -> Seat Bid Object -> Bid Object -> id" attribute.
${AUCTION_AD_ID} - ID of the ad markup the bidder wishes to serve; from "Bid Response Object -> Seat Bid Object -> Bid Object -> adid" attribute.
${AUCTION_PRICE} - Settlement price using the same currency and units as the account; from "Bid Response Object -> Seat Bid Object -> Bid Object -> price" attribute.
${AUCTION_CURRENCY} - The currency used in the bid (explicit or implied); for confirmation only.
```

Example:

```
https://mysite.com/my_notification_url?id=${AUCTION_ID}&bidid=${AUCTION_BID_ID}&price=${AUCTION_PRICE}&currency=${AUCTION_CURRENCY}
```

If you are using both **nURL** and **bURL**, ExoClick will make a call to both of them.

### Examples <a href="#examples" id="examples"></a>

## No Bid Response <a href="#no-bid-response" id="no-bid-response"></a>

To answer to a bid request without making an actual bid, an HTTP response code 204 "No Content" should be sent.

## Win and Billing Notification URLs <a href="#win-and-billing-notification-urls" id="win-and-billing-notification-urls"></a>

If either the **nURL** or the **bURL** are in the bid response and are valid URLs, ExoClick platform will send a GET request to them. These URLs can have a few tokens to be replaced by ExoClick before doing the GET:

```
${AUCTION_ID} - ID of the bid request; from "Bid Request Object -> id" attribute.
${AUCTION_BID_ID} - ID of the bid; from "Bid Response Object -> bidid" attribute.
${AUCTION_IMP_ID} - ID of the impression just won; from "Bid Request Object -> Impression Object -> id" attribute.
${AUCTION_SEAT_ID} - ID of the bidder seat for whom the bid was made; from "Bid Response Object -> Seat Bid Object -> Bid Object -> id" attribute.
${AUCTION_AD_ID} - ID of the ad markup the bidder wishes to serve; from "Bid Response Object -> Seat Bid Object -> Bid Object -> adid" attribute.
${AUCTION_PRICE} - Settlement price using the same currency and units as the account; from "Bid Response Object -> Seat Bid Object -> Bid Object -> price" attribute.
${AUCTION_CURRENCY} - The currency used in the bid (explicit or implied); for confirmation only.
```

Example:

```
https://mysite.com/my_notification_url?id=${AUCTION_ID}&bidid=${AUCTION_BID_ID}&price=${AUCTION_PRICE}&currency=${AUCTION_CURRENCY}
```

If you are using both **nURL** and **bURL**, ExoClick will make a call to both of them.

## Examples <a href="#examples" id="examples"></a>

You can find detailed examples of the Responses you can receive in the [example page](/rtb/advertisers/open-rtb/open-rtb-adv-code-examples-2.5.md).

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.exoclick.com/rtb/advertisers/open-rtb/adv-open-rtb-2.5-response.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.