ExoClick RTB Bid Request Specifications

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	Descripción
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)
tipo	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)
talla	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

Ejemplos

You can find a complete list of all the types of requests you can receive in our Advertiser Request example page.