> For the complete documentation index, see [llms.txt](https://docs.exads.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.exads.com/rtb/advertisers/open-rtb/open-rtb-advertisers.md).
# Open RTB Integration for Advertisers
This documentation explains how Advertisers can integrate their platforms with EXADS using the OpenRTB standard.
## Bid Request/Response Specifications
* [Open RTB Bid Request Specifications](/rtb/advertisers/open-rtb/open-rtb-advertisers-request.md)
* [Open RTB Bid Response Specifications](/rtb/advertisers/open-rtb/open-rtb-advertisers-response.md)
## Requirements
The EXADS 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), but with a few limitations/requirements.
* Supported pricing models:
* Banner, Popunder, In-Stream Ads: CPM
* Push Notification, Native Ads: CPM or CPC \*
* Number of bids per request:
* For Banner, Popunder, In-stream and Push Notification Ads - one bid per request only (One impression object)
* For Native Ads - multiple bids per request are supported
* Creative (ad markup) must be supplied directly in the bid response
* The ad markup **must** respect the EXADS XML Ad Markups
* The currency of the bid price is the currency of your EXADS account (EUR or USD)
* The advertiser must provide a valid RTB URL, this can have any GET params that might be needed by the endpoint and must be able to receive the bid request through HTTP POST
\* Pricing model to be defined in bid response.
### Supported Ad Types
* Banner Ads: Image and iFrame
* Direct Links
* Email Clicks
* Fullpage Interstitial (Desktop & Mobile)
* In-Stream
* Native Ads
* Popunder
* Push Notification Ads: 720 x 480 and 192 x 192
## 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 EXADS RTB requests, you may whitelist [IP Networks](https://docs-advanced.exads.com/docs/rtb-advertisers/ip-networks/ip-networks).
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.exads.com/rtb/advertisers/open-rtb/open-rtb-advertisers.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.