Docs v2.0\Publisher\Feed

Publisher JSON Feed

Introduction

This is an integration guide for RebornAds demand feed. The integration is done via HTTP GET request.
Both http and https are supported.

Base Url: http://api.rebornads.com/api/v2.0

Pop Request docs
Push Request docs
InPage Push Request docs
Tips

Pop Request

GET /pop/:feedId/:auth

Parameter	Description	Example
feed	[Required] Feed ID (numeric)	23783
auth	[Required] Auth secret	sdj9jek
user_ip	[Required] IPv4 address	128.32.42.23
ua	[Required] User Agent string	Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.70 Safari/537.36
url	[Required] User referrer URL	example.com
query	[Optional] Keyword or search string.	shopping
subid	[Optional] Subsource identifier (string)	238rhf93
lang	[Optional] Request ad language	en
accept_language	[Optional] User Accept-Language header	en,en-US;q=0.9,ca;q=0.7
Header	Description	Example
Accept-Language	User Accept-Language header	en,en-US;q=0.9,ca;q=0.7

Pop Response

The response is a JSON object. In a case of no results, an HTTP code 204 will be returned.

Successful response:

{
  "title": "...",
  "descr": "...",
  "bid": 0.000101,
  "url": "http://t.rebornads.com/c/XXXXX_0",
}

NOTE: pixel, icon or image will might be missing in some cases.

Error response:

{"err":1, "errdesc": "User IP parameter is missing or wrong"}

Push Request

GET /push/:feedId/:auth

Parameter	Description	Example
feed	[Required] Feed ID (numeric)	23783
auth	[Required] Auth secret	sdj9jek
user_ip	[Required] IPv4 address	128.32.42.23
ua	[Required] User Agent string	Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.70 Safari/537.36
url	[Required] User referrer URL	example.com
query	[Optional] Keyword or search string.	shopping
subid	[Optional] Subsource identifier (string)	238rhf93
lang	[Optional] Request ad language	en
accept_language	[Optional] User Accept-Language header	en,en-US;q=0.9,ca;q=0.7
subscription_date	User subscription date (Format "YYYY-MM-DD hh:mm:ss", ie "2019-07-22 12:32:41")	json
Header	Description	Example
Accept-Language	User Accept-Language header	en,en-US;q=0.9,ca;q=0.7

Push Response

The response is a JSON object. In a case of no results, an HTTP code 204 will be returned.

Successful response:

{
  "title": "...",
  "descr": "...",
  "bid": 0.053100,
  "url": "http://t.rebornads.com/c/XXXXX_0",
  "icon": "http://t.rebornads.com/ic/XXXXX_0",
  "image": "http://t.rebornads.com/im/XXXXX_0",
}

NOTE: image might be empty.

Error response:

{"err":1, "errdesc": "User IP parameter is missing or wrong"}

InPage Push Request

GET /inpage_push/:feedId/:auth

Parameter	Description	Example
feed	[Required] Feed ID (numeric)	23783
auth	[Required] Auth secret	sdj9jek
user_ip	[Required] IPv4 address	128.32.42.23
ua	[Required] User Agent string	Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.70 Safari/537.36
url	[Required] User referrer URL	example.com
query	[Optional] Keyword or search string.	shopping
subid	[Optional] Subsource identifier (string)	238rhf93
lang	[Optional] Request ad language	en
accept_language	[Optional] User Accept-Language header	en,en-US;q=0.9,ca;q=0.7
Header	Description	Example
Accept-Language	User Accept-Language header	en,en-US;q=0.9,ca;q=0.7

InPage Push Response

The response is a JSON object. In a case of no results, an HTTP code 204 will be returned.

Successful response:

{
  "title": "...",
  "descr": "...",
  "bid": 0.053100,
  "url": "http://t.rebornads.com/c/XXXXX_0",
  "image": "http://t.rebornads.com/im/XXXXX_0",
}

Error response:

{"err":1, "errdesc": "User IP parameter is missing or wrong"}

Tips

Since this kind of activity is designed to work on a large scale, here are some optimization tips to boost the performance:

HTTP Keep-Alive / HTTP/2

It is recommended to turn on HTTP Keep-Alive to reuse the same TCP socket for multiple requests. HTTP/2 protocol allows multiple concurrent requests to be sent over a single connection.

HTTP Compression

Reduce bandwidth usage by activating HTTP compression.

Use HTTP instead of HTTPS

SSL requires additional work by the severs on both ends (publisher and advertiser). Although both http and https are supported, it is recommended to use http. Note that for the clicks/impressions and for the statistics API it is still recommended to use https.