Documentation

Documentation

  • General
  • Advertisers
  • Publishers
  • RTB
  • API
  • News

›Open RTB

Advertisers

  • Advertisers RTB Overview
  • Ad Exchange Partners
  • Integrating Advertising Demand
  • Open RTB

    • Open RTB Integration
    • Open RTB 2.4 Bid Request
    • Open RTB 2.4 Bid Response
    • Open RTB 2.5 Bid Request
    • Open RTB 2.5 Bid Response
    • Prebid / OpenRTB 2.5 Bid Request
    • Prebid / OpenRTB 2.5 Bid Response

    EXADS RTB

    • EXADS RTB Integration
    • EXADS RTB Bid Request
    • EXADS RTB Bid Response

Publishers

  • Publishers RTB Overview
  • Ad Exchange Partners
  • Integrating Publishing Supply
  • Open RTB

    • Open RTB Integration
    • Open RTB 2.4 Bid Request
    • Open RTB 2.4 Bid Response
    • Open RTB 2.5 Bid Request
    • Open RTB 2.5 Bid Response
    • Prebid / Open RTB 2.5 Bid Request
    • Prebid / Open RTB 2.5 Bid Response

    EXADS RTB

    • EXADS RTB Integration
    • EXADS RTB Bid Request
    • EXADS RTB Bid Response

IP Networks

  • IP Networks

Open RTB Integration for Publishers

  This documentation explains how partners can integrate their platforms with EXADS using the OpenRTB standard to sell their traffic.

Bid Request/Response Specifications

  • Open RTB Bid Request Specifications
  • Open RTB Bid Response Specifications

Requirements

EXADS RTB API strictly follows the OpenRTB v2.4 Specifications, but with a few limitations/requirements.

  • One bid per request only (One impression object).
  • The bid price can be either CPM or CPC based on exchange configuration.
  • Creative (ad markup) is directly supplied in the bid response.
  • The ad markup will respect the EXADS XML Ad Markups.
  • The currency of the bid price will be the currency of your EXADS account (EUR or USD).  

Supported ad types

  • 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

 

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.  
← Integrating Publishing SupplyOpen RTB 2.4 Bid Request →
  • Bid Request/Response Specifications
  • Requirements
  • Supported ad types
  • Best Practices
Documentation
Community
Github
Useful Links
EXADS
Copyright © 2025 EXADS