Notification for loss reason

Yandex supports lurl, which is specified in the DSP's response in the seatbid.bid.lurl field. Additionally, DSPs can be configured to send loss reasons to a separate URL (sent via POST method in JSON format (Content-Type: application/json)). If you wish to enable this feature, please contact your manager or at newpartners@yandex-team.ru.

{
  "notifications": [
    {
      "crid": "(string)",
      "requestid": "(string)",
      "impressionid": "(string)",
      "status": "(int)",
      "reasons": "(repeated int32)",
      "payload": "(string)"
    }
  ]
}

Request parameters

Parameter	Description	Required
Bid Loss Notification object
notifications	Array of Notifications objects. Each object corresponds to a separate bid.	Yes
Notifications object
crid	The ID of the creative.	Yes
requestid	ID of the auction, assigned by the RTB host.	Yes
impressionid	ID of the ad unit on the HTML page.	No
status	Reason for rejecting the bid. Acceptable values: 0 — Bid won. 1 — Internal error. For more information, contact your manager or write to newpartners@yandex-team.ru. 3 — Invalid JSON in the DSP response. 9 — Bid price is invalid or missing. 102 — Bid lost. 200 — Creative rejected for unknown reasons. 201 — Creative hasn't passed moderation yet. 202 — Creative rejected because of moderation results. 203 – The dimensions (w/h) of the creative in the response do not match the dimensions from the request. 204 – Incorrect format of the creative. 205 — The advertiser domain is filtered by the site settings. 209 – The category of the creative is filtered by the site's settings. 214 – SKAdN version not supported on the request. 1001 — Missing cid in the DSP response. 1002 — Creative requires supporting documents to pass moderation. 1111 — OpenBidding bid lost. 1347 – ERID is not passed in the BidResponse. For more information, see the documentation. 1413 – Adm size is higher than the acceptable payload.	Yes
reasons	Reasons for rejecting moderation. You can view the value of a specific error using a link of the `https://yandex.ru/support/direct-tooltips/modadvert-XXX.html` form where `XXX` is the value of the reasons field.	yes if the `status` value is 202
payload	An arbitrary string that's obtained from the DSP response.	No

Response example

{
  "notifications": [
    {
      "crid": "TPL166_AD5026703",
      "requestid": "65724453146892921",
      "impressionid": "1",
      "status": 202,
      "reasons": [
        359
      ],
      "payload": "some string from response seatbid[0].bid[0].payload"
    }
  ]
}

Was the article helpful?

Formats and mechanics

Annex