Openrtb 2 6 Quickstart

This article walks through the most common implementation path for the topic above. It assumes you have an active TrendBuzz seat and at least one OpenRTB-compatible endpoint configured.

Prerequisites

A TrendBuzz seat in active status.
An OpenRTB 2.5 or 2.6 endpoint reachable over HTTPS.
For publishers: a valid sellers.json entry and ads.txt / app-ads.txt file.
For advertisers: a verified billing entity and payment method.

Quick start

From the dashboard, navigate to Integrations → Endpoints and copy your bidder URL.
POST a sample bid request (see payload below). The response should arrive within the configured timeout (120ms hard cap).
Inspect the win notice URL emitted in the bid response.
Once you have received your first billable impression, the dashboard will show throughput within 10 minutes.

Sample bid request

{
  "id": "tb-bid-7f3d49c1",
  "imp": [{ "id": "1", "banner": { "w": 300, "h": 250 }, "tagid": "homepage-mrec" }],
  "site": { "domain": "example.com", "page": "https://example.com/article/12" },
  "device": { "ua": "Mozilla/5.0", "ip": "203.0.113.5", "geo": { "country": "USA" } },
  "user": { "id": "anon-cohort-AX-9" },
  "at": 1,
  "tmax": 120,
  "regs": { "ext": { "gpp": "DBABLA~BVQqAAAAAgA.QA" } },
  "source": { "ext": { "schain": { "complete": 1, "ver": "1.0", "nodes": [
    { "asi": "trendbuzz.to", "sid": "tb-seller-001", "hp": 1 }
  ]}}}
}

What can go wrong

Timeouts: Bidder must respond inside 120ms. We recommend a 95ms internal budget.
Schema: Use the OpenRTB validator under Tools → Validator.
Win notice not firing: Confirm your win endpoint accepts cross-region pings.

Next steps

Once your integration is live, enable log-level export for full transparency, and read the SupplyChain Object setup guide.