For the complete documentation index, see llms.txt. Markdown versions of documentation pages are available by appending .md to page URLs.
Skip to content

EXADS RTB Bid Request Specifications


Note: The EXADS RTB Bid Request is done using JSON for POST.


Bid Request Headers

  • EXADS 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

EXADS allows one HTTP method for requests: POST.

When requesting bids for a specific context, the platform performs an HTTP request with a timeout of 300ms. It sends 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

* mandatory fields ** mandatory only for type banner

Bid Request POST: JSON


Note: EXADS POST Bid requests are done using JSON only, so there are no XML examples below.


Popunder: JSON

Push Notifications 720x480: JSON

Push Notifications 192 x 192: JSON

Here size parameter may be omitted. It will just be assumed as 192x192 by default for backwards compatibility.

Last updated

Was this helpful?