> For the complete documentation index, see [llms.txt](https://adagio-io.gitbook.io/adagio-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://adagio-io.gitbook.io/adagio-documentation/openrtb-s2s-endpoint/all-supported-openrtb-parameters/bid-response-objects-and-parameters.md).

# Bid Response objects and parameters

The BidResponse contains one or more SeatBids, each with Bids specifying creative details, price, and targeting. Mandatory fields must follow the OpenRTB spec, while optional fields can improve targeting, analytics, and performance with Adagio’s DSP partners.

{% hint style="info" %}
Adagio populates as many fields as possible among those listed below.\
The actual content of each response depends on:

* the information provided in the original ad request,
* the data returned by bidders in their bid responses.
  {% endhint %}

### 1. `bidresponse` object

<table data-full-width="true"><thead><tr><th width="126.73828125">Field</th><th width="170.70703125">Type</th><th>Description</th></tr></thead><tbody><tr><td><code>id</code></td><td>string</td><td><strong>ID of the of the bidRequest to which this is a response</strong></td></tr><tr><td><code>seatbid</code></td><td>array of <a href="/pages/Q1HXKf6s7dwLszfcw7xw#id-5.2-seatbid-object">objects</a></td><td>Array of <a href="#id-2.-seatbid-object"><code>seatbid</code> objects</a>; with at least 1 entry is a bid is to be made.</td></tr><tr><td><code>bidid</code></td><td>string</td><td><strong>Bidder generated response ID</strong> to assist with logging/tracking.</td></tr><tr><td><code>cur</code></td><td>string;<br>default "USD"</td><td><strong>Bid currency.</strong> Refer to <a data-mention href="/adagio-documentation/operations-and-support/standards-and-compliance/supported-currencies.md">Supported Currencies</a></td></tr><tr><td><code>nbr</code></td><td>integer</td><td>Reason for not bidding. <mark style="color:$danger;">Due to cost optimisation, Adagio uses HTML request's headers error codes instead of <code>nbr</code> codes in their body.</mark></td></tr></tbody></table>

### 2. `seatbid` object

<table data-full-width="true"><thead><tr><th width="129.98828125">Field</th><th width="170.70703125">Type</th><th>Description</th></tr></thead><tbody><tr><td><code>seat</code></td><td>string</td><td><strong>ID of the demand partner seat</strong> on Adagio's platform.</td></tr><tr><td><code>bid</code></td><td>array of <a href="#id-3.-bid-object">objects</a></td><td>Array of <a href="#id-3.-bid-object"><code>bid</code> objects </a>for impressions.</td></tr></tbody></table>

### 3. `bid` object

<table data-full-width="true"><thead><tr><th width="128.01953125">Field</th><th width="172.765625">Type</th><th>Description</th></tr></thead><tbody><tr><td><code>id</code></td><td>string</td><td><strong>Bidder-generated bid ID</strong>.</td></tr><tr><td><code>impid</code></td><td>string</td><td><strong>ID of the impression</strong> being bid on.</td></tr><tr><td><code>price</code></td><td>float</td><td><strong>Bid price CPM</strong> in currency specified.</td></tr><tr><td><code>adm</code></td><td>string</td><td>Optional means of conveying <strong>ad markup</strong> (e.g., HTML, VAST XML) in case the bid wins; supersedes the win notice if markup is included in both. Substitution macros (Refer to <a href="https://github.com/InteractiveAdvertisingBureau/openrtb2.x/blob/main/2.6.md#44---substitution-macros-">IAB Section 4.4</a>) may be included.</td></tr><tr><td><code>crid</code></td><td>string</td><td><strong>Creative ID to assist</strong> with ad quality checking .</td></tr><tr><td><code>nurl</code></td><td>string</td><td><strong>Win notice URL</strong> called by the exchange if the bid wins (not necessarily indicative of a delivered, viewed, or billable ad); optional means of serving ad markup. Substitution macros (Refer to <a href="https://github.com/InteractiveAdvertisingBureau/openrtb2.x/blob/main/2.6.md#44---substitution-macros-">IAB Section 4.4</a>) may be included in both the URL and optionally returned markup.</td></tr><tr><td><code>burl</code></td><td>string</td><td><strong>Billing notice URL</strong> called by the exchange when a winning bid becomes billable based on exchange-specific business policy (e.g., typically delivered, viewed, etc.). Substitution macros (Refer to <a href="https://github.com/InteractiveAdvertisingBureau/openrtb2.x/blob/main/2.6.md#44---substitution-macros-">IAB Section 4.4</a>) may be included.</td></tr><tr><td><code>lurl</code></td><td>string</td><td><strong>Loss notice URL</strong> called by the exchange when a bid is known to have been lost based on exchange-specific business policy (e.g., typically delivered, viewed, etc.). Substitution macros (Refer to <a href="https://github.com/InteractiveAdvertisingBureau/openrtb2.x/blob/main/2.6.md#44---substitution-macros-">IAB Section 4.4</a>) may be included.</td></tr><tr><td><code>adid</code></td><td>string</td><td><strong>ID of a preloaded ad</strong> to be served if the bid wins</td></tr><tr><td><code>bundle</code></td><td>string</td><td><strong>App bundle or package name</strong>.</td></tr><tr><td><code>cat</code></td><td>string array</td><td><strong>Creative IAB category</strong>. The taxonomy to be used is defined by the <code>cattax</code> field.</td></tr><tr><td><code>cattax</code></td><td>integer;<br>default 1</td><td>The <strong>taxonomy in use.</strong> Refer to <a href="https://github.com/InteractiveAdvertisingBureau/AdCOM/blob/master/AdCOM%20v1.0%20FINAL.md#list_categorytaxonomies">List: Category Taxonomies</a> for values.</td></tr><tr><td><code>attr</code></td><td>integer array</td><td><strong>Creative attributes</strong>.</td></tr><tr><td><code>language</code></td><td>string</td><td><strong>Language</strong> of creative (ISO-639-1).</td></tr><tr><td><code>adomain</code></td><td>string array</td><td><strong>Advertiser domain</strong> for block list checking (e.g., “ford.com”). This can be an array of for the case of rotating creatives.</td></tr><tr><td><code>apis</code></td><td>integer array</td><td><strong>List of supported APIs for the markup</strong>. If an API is not explicitly listed, it is assumed to be unsupported. Refer to <a href="https://github.com/InteractiveAdvertisingBureau/AdCOM/blob/main/AdCOM%20v1.0%20FINAL.md#list_apiframeworks">List: API Frameworks</a> in AdCOM 1.0.</td></tr><tr><td><code>protocol</code></td><td>integer</td><td><strong>Video response protocol</strong> of the markup if applicable. Refer to <a href="https://github.com/InteractiveAdvertisingBureau/AdCOM/blob/master/AdCOM%20v1.0%20FINAL.md#list--creative-subtypes---audiovideo-">List: Creative Subtypes - Audio/Video</a> in AdCOM 1.0.</td></tr><tr><td><code>exp</code></td><td>integer</td><td>Advisory as to the <strong>number of seconds the bidder is willing to wait between the auction and the actual impression.</strong> <mark style="color:$warning;">Violating this might result in ignored billable impression or IVT.</mark></td></tr><tr><td><code>dur</code></td><td>integer</td><td><strong>Duration of the video</strong> creative in seconds if applicable.</td></tr><tr><td><code>mtype</code></td><td>integer</td><td><strong>Type of the creative markup</strong> so that it can properly be associated with the right sub-object of the <code>BidRequest.Imp.</code><br>Values:<br>1 = Banner<br>2 = Video,<br>3 = Audio<br>4 = Native</td></tr><tr><td><code>w</code></td><td>integer</td><td><strong>Width</strong> of the creative in device-independent pixels (DIPS).</td></tr><tr><td><code>h</code></td><td>integer</td><td><strong>Height</strong> of the creative in device-independent pixels (DIPS).</td></tr><tr><td><code>wratio</code></td><td>integer</td><td><strong>Relative width</strong> of the creative when expressing size as a ratio.</td></tr><tr><td><code>hratio</code></td><td>integer</td><td><strong>Relative height</strong> of the creative when expressing size as a ratio.</td></tr></tbody></table>

## References

* [OpenRTB 2.6 Spec](https://github.com/InteractiveAdvertisingBureau/openrtb2.x/blob/main/2.6.md)
* [OpenRTB 2.6 Community extensions](https://github.com/InteractiveAdvertisingBureau/openrtb/tree/main/extensions/community_extensions)
* [OpenRTB 2.6 Official extensions](https://github.com/InteractiveAdvertisingBureau/openrtb/tree/main/extensions/2.x_official_extensions)


---

# 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://adagio-io.gitbook.io/adagio-documentation/openrtb-s2s-endpoint/all-supported-openrtb-parameters/bid-response-objects-and-parameters.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.