← Bidnelio

Integration guide.

Server-side OpenRTB

POST JSON to your assigned HTTPS bidder origin at /rtb/ssp/SSP_ID. Use Authorization: Bearer with the SSP key issued in the cabinet. Keep this key on your server. OpenRTB 2.5 / 2.6, at=1, USD, one impression and one media format per request. Multi-impression requests and ad pods are not supported.

{
  "id": "publisher-request-id",
  "at": 1,
  "cur": [
    "USD"
  ],
  "tmax": 300,
  "site": {
    "domain": "your-authorized-domain.example"
  },
  "imp": [
    {
      "id": "1",
      "tagid": "your-placement-id",
      "bidfloor": 0.5,
      "bidfloorcur": "USD",
      "banner": {
        "w": 300,
        "h": 250
      }
    }
  ]
}

Publisher banner tag

Create an authorized website and banner placement in the cabinet, then copy its generated script from “Sites and apps”. The public placement token is restricted to its registered domain. The SSP key is never included in browser code. The creative is rendered in a sandboxed iframe; billing is recorded on its load event. This measures a rendered creative event, not viewability. The tag reads TCF consent from an existing CMP and never fabricates user consent.

Video, audio and native

Use the assigned OpenRTB endpoint for VAST and Native 1.2 requests. VAST supply and demand connectors support compatible player integrations. Prebid Server connections require a configured external Prebid Server account and bidder parameters. Bidnelio is not yet a registered Prebid.js bidder adapter.

ads.txt and app-ads.txt

After authorization and assignment of a seller ID, place the cabinet-generated line at /ads.txt on the publisher website. Apps use /app-ads.txt on the developer website referenced in the app store. Use DIRECT only for the direct contractual relationship with Bidnelio. Additional partner lines must be supplied and agreed by the relevant partner; do not invent IDs.

sellers.json and supply chain

The API publishes authorized seller records at /api/public/sellers.json. The production website must proxy /sellers.json to that endpoint. Before a live integration, verify that publisher declarations, seller IDs and schain agree. No sellers are advertised before authorization.

Reports and commercial events

nurl records a win; burl records the agreed billable event. Reporting uses UTC. Requests use auction time; wins and charges use callback time. Charges represent accrued amounts, not settled payments.

Contact integration team ↗