Ad Exchange

Real-time bidding for your ad network.

Connect an ad network, offerwall, or exchange to Highpay Ads. Send a banner slot, the auction picks a bid, and the winning ad comes back ready to show.

  • Ad networks, offerwalls, faucets, and Web3 sites
  • One OpenRTB request for each banner slot
  • The impression is recorded when the ad is shown

Live auction

Sample data
OpenRTB 2.5
network-site.com
300×250
POST /api/v1/rtb/bid300×250
Bid requestreq_539db4
imp.banner300×250
site.domainnetwork-site.com
device.geoIN
bidfloor$0.04 CPM
Bids (CPM)Floor $0.04
NNova Wallet—
AAtlas Games—
OOrbit DEX—
LLumen Bridge—
Collecting bids…··

01Request

02Auction

03Render

04Win notice

How the exchange works.

Each auction cycles through a different supply partner and format. Watch the request, the bids, the render, then the win notice.

01

A partner sends the slot

An ad network, offerwall, faucet, or Web3 site makes one banner placement available, with the page domain and the visitor.

02

Highpay runs the auction

Eligible bids are checked against price, floor, country, format, and traffic quality. The winning bid is the one that clears.

03

The ad comes back

You render the returned HTML in that slot. If nothing clears the floor, the response is empty and you move on.

04

The show is recorded

Call the win notice when the ad is on screen. That notice records the impression. The bid itself does not.

More than a redirect. The exchange takes one banner slot, runs the auction, and returns HTML. The impression counts when the ad is shown.

Who connects
Ad networks300×250
Offerwalls300×250
Faucets728×90
Web3 sites468×60

Built for networks

Ad networks, offerwalls, faucets, and Web3 sites each send their own inventory into the same auction.

POST /api/v1/rtb/bidJSON

banner 300×250

site example-publisher.com

bidfloor 0.04 USD

one slot per request

No fill returns an empty 204

One request, one slot

OpenRTB 2.5. Send a single banner impression and render the HTML that comes back.

When it bills
Bid responseNot billed
Win noticeBilled once
Test keyNever bills

Bill when it shows

A bid does not charge anyone. The first win notice records the impression. Test keys stay free.

What you connect.

Supply partners request Highpay banners. Demand partners reach the publisher network. Both paths are documented.

Supply from your network

Pull Highpay banner demand into ad networks, offerwalls, faucets, and Web3 sites with the same publisher API key as Smart Links.

Demand on the other side

Ad networks, DSPs, exchanges, and media buyers can connect as demand and reach Web3 publisher inventory. The integration guide covers that path.

Standard banner sizes

Live creatives fill 300×250, 728×90, 160×600, and 468×60. Each size is reported on its own Banner API zone.

Traffic stays checked

Country, format, floor, and traffic quality decide which campaigns can bid. Live keys require a verified, active publisher.

Test before you go live

A test key returns a sample banner so you can wire the slot. Win notices on that key never bill.

Revenue in your stats

Banner API zones sit next to your site zones in publisher statistics, so exchange fill is visible on its own.

Start with the integration guide.

The guide walks through supply and demand. The API reference has the bid request, the HTML response, and the win notice.