Documentation

Everything you need to connect to GFY Bid: how to send us bid requests, how to answer ours, and how to read your statistics by API.

You send us OpenRTB 2.5 bid requests and receive our bids.

We send you bid requests; you answer with bids and a billing notice URL.

Your statistics with us — requests, bids, impressions and money — by API.

Popunder, SSP, DSP, bidfloor, burl, nurl, first-price, QPS — in plain words.

At a glance

Protocol	OpenRTB 2.5, JSON over HTTP POST (no compression)
Ad format	Popunder: `adm` is a URL
Auction	First price (`at` = 1); prices are CPM in USD
Time limit	`tmax` up to 250 ms; we answer within `tmax` or with no bid
Billing	Only the billing notice (`burl`) counts an impression
Win notice	`nurl`, for statistics only
No bid	HTTP 204 (on request: HTTP 200 with an empty body)
Currency	USD only
Report time zone	UTC by default, any IANA time zone in the request

Contact us through the contact form or at manager@gfybid.com.
Publishers receive a personal bid endpoint. Advertisers give us their bid endpoint and the domains of their billing and win notices.
We agree the request rate (QPS), filters and, if you wish, a daily reconciliation with your reporting API.
Your account manager issues a key for our reporting API.

Host names in the examples (example.net) and all identifiers are placeholders. The real addresses come with your endpoint.

Availability. Two relay instances behind a load balancer; releases without downtime.
Location. Dedicated servers in the EU (France). The network round trip to Frankfurt and Amsterdam is about 5–15 ms.
Billing records. Every billing notice is stored before we answer it; a repeated notice is never counted twice.
Contacts. Your account manager — for business and technical questions alike.

Questions about the integration? Write to manager@gfybid.com or use the contact form.