> For the complete documentation index, see [llms.txt](https://docs.digitalturbine.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digitalturbine.com/dt-ads-demand/dt-exchange-openrtb-2.5-specs/supported-auction-macros.md).

# Supported Auction Macros

DT allows you to substitute macros based on the [OpenRTB API Specification Version 2.5](https://www.iab.com/wp-content/uploads/2016/03/OpenRTB-API-Specification-Version-2-5-FINAL.pdf) in the `nurl` or `burl` fields, or within the tracking pixel in the `adm` field for auctions. The following table describes the supported DT auction macros.

| Macro                   | Description                                                                                                                                                          |
| ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `${AUCTION_PRICE}`      | <p>The settlement price of the auction.<br>This macro is required in any bid response; otherwise, the bid is considered invalid.</p>                                 |
| `${AUCTION_ID}`         | ID of the bid request: From the [BidRequest.id](/dt-ads-demand/dt-exchange-openrtb-2.5-specs.md#object-bidrequest) attribute.                                        |
| `${AUCTION_BID_ID}`     | ID of the bid: From the [BidRequest.id](/dt-ads-demand/dt-exchange-openrtb-2.5-specs.md#object-bidrequest) attribute.                                                |
| `${AUCTION_IMP_ID}`     | ID of the impression won: From the [imp.id](/dt-ads-demand/dt-exchange-openrtb-2.5-specs.md#object-imp) attribute.                                                   |
| `${AUCTION_SEAT_ID}`    | ID of the bidder seat for whom the bid is made.                                                                                                                      |
| `${AUCTION_AD_ID}`      | ID of the ad markup the bidder wishes to serve: From the [`bid.adid`](/dt-ads-demand/dt-exchange-openrtb-2.5-specs.md) attribute.                                    |
| `${AUCTION_CURRENCY}`   | The currency used in the bid. Digital Turbine only supports USD.                                                                                                     |
| `${AUCTION_MIN_TO_WIN}` | <p>The minimum bid the bidder needs to win the auction.<br>Supported in the <a href="/pages/hE4MWglX3jpV4wxbN78i#object-seatbid">seatbid.bid.nurl</a> attribute.</p> |
| `${AUCTION_LOSS}`       | Auction loss reason code.                                                                                                                                            |


---

# 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.digitalturbine.com/dt-ads-demand/dt-exchange-openrtb-2.5-specs/supported-auction-macros.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.
