> 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/exoclick-rtb/bid-request.md).

# ExoClick RTB Bid Request

This page describes the different components of the RTB requests you will receive in order to bid.

## Bid Request Headers

* **ExoClick RTB Version HTTP Header**: `x-exadsrtb-version: 1.0`
* **Keep-Alive HTTP Header**: `Connection: Keep-Alive`
* **Content JSON**: `Content-Type: application/json`
* **Data Encoding Header**: `Accept-Encoding`

## Bid Request Object

When requesting bids for a specific context, the platform will perform an HTTP request with a timeout of **300ms**. It will send the following object encoded as JSON in the request body as POST:

| Attribute         | Description                                                                                                                                            |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
| id                | Unique bid request ID (string)\*                                                                                                                       |
| ip                | IP address of the user (string)\*                                                                                                                      |
| language          | Browser language using ISO-639-1-alpha-2 (string)\*                                                                                                    |
| remote\_addr      | Main IP address of the user (string)                                                                                                                   |
| x\_forwarded\_for | X-FORWARDED-FOR IP address of the user or empty if not set (string)                                                                                    |
| type              | Request type. Can be "banner", "popunder" or "push\_notification" (string)\*                                                                           |
| ua                | Browser user agent (string)\*                                                                                                                          |
| url               | Full URL of the page where the ad will be shown (string)\*                                                                                             |
| user\_id          | Unique user ID (string)\*                                                                                                                              |
| export            | Response type. Can be "json" or "xml" (string)\*                                                                                                       |
| keyword           | keyword (string)                                                                                                                                       |
| size              | Publisher ad type size (string)\*\*                                                                                                                    |
| sub               | The sub will be an integer number representing the ID of the zone where the request was originated from (not to be confused with the {zone\_id} token) |

\*mandatory fields

\*\*mandatory only for type banner. On Push Notification, it will be assumed 192x192 if empty

## Examples

You can find a complete list of all the types of requests you can receive in our [Advertiser Request example page](/rtb/advertisers/exoclick-rtb/exoclick-rtb-advertiser-code-examples.md).


---

# 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/exoclick-rtb/bid-request.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.