> 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/open-rtb.md).

# Open RTB Integration for Advertisers

This documentation explains how Advertisers can integrate their platforms with ExoClick using the OpenRTB standard.

## Bid Request/Response Specifications

* [Open RTB 2.4 Bid Request Specifications](/rtb/advertisers/open-rtb/adv-open-rtb-2.4-request.md)
* [Open RTB 2.4 Bid Response Specifications](/rtb/advertisers/open-rtb/adv-open-rtb-2.4-response.md)
* [Open RTB 2.5 Bid Request Specifications](/rtb/advertisers/open-rtb/adv-open-rtb-2.5-request.md)
* [Open RTB 2.5 Bid Response Specifications](/rtb/advertisers/open-rtb/adv-open-rtb-2.5-response.md)

## Requirements

ExoClick RTB API strictly follows the [OpenRTB v2.4 Specifications](http://www.iab.com/wp-content/uploads/2016/03/OpenRTB-API-Specification-Version-2-4-FINAL.pdf) and [OpenRTB v2.5 Specifications](https://www.iab.com/wp-content/uploads/2016/03/OpenRTB-API-Specification-Version-2-5-FINAL.pdf), but with a few limitations/requirements.

* Number of bids per request:
  * For all ad formats - one bid per request only (One impression object)
  * For Native Ads - multiple bids per request are supported
* The ad markup **must** respect the ExoClick XML Ad Markups
* Creative (ad markup) must be supplied directly in the bid response
* The currency of the bid price will be the currency of your ExoClick account (EUR or USD)
* The advertiser will need to provide a valid RTB URL, this can have any GET params that might be needed by the endpoint and must be able to receive our bid request through HTTP POST

## Supported Ad Types and Price Models

| Ad format                                                                                                                                  | Price model       |
| ------------------------------------------------------------------------------------------------------------------------------------------ | ----------------- |
| Banner (Image and Iframe), Fullpage Interstitial (Image and Iframe), Popunder, In-Stream, Native, Push Notifications (192x192 and 720x480) | CPM               |
| Direct Link, Email Clicks                                                                                                                  | CPC and Smart CPC |

Pricing model is defined in the bid response.

## Supported ad types Open RTB 2.4 & 2.5

* Banner
* Direct Links
* Email Clicks
* Video (In-Stream Video, Outstream Video, Video Slider)
* Native Ads
* Popunder
* Push Notifications: 720 x 480 and 192 x 192
* Interstitial

## Best Practices

* One of the simplest and most effective ways of improving connection performance is to enable HTTP Persistent Connections, also known as **Keep-Alive**. This has a profound impact on overall performance by reducing connection management overhead as well as CPU utilization on both sides of the interface.
* The OpenRTB specifications do not cover security other than **recommending plain HTTP** for performance reasons. If you need to authorize ExoClick RTB requests, you may whitelist [IP Networks](/rtb/advertisers/exoclick-rtb/ip-networks.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/open-rtb/open-rtb.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.