Notification for reason for loss

The reason for loss is sent using the POST method in JSON format (Content-Type: application/json).

For lost bids, Yandex can send a POST request with JSON to a separate URL with the reasons why the bid was lost. To enable this feature, contact your manager or write to dsp@yandex-team.ru.

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

Request parameters
Bid Loss Notification object
Parameter	Description	Required
`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 dsp@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. 205: The advertiser domain is filtered by the site settings. 1001: Missing cid in the DSP response. 1002: Creative requires supporting documents to pass moderation.	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

Request parameters
Bid Loss Notification object
Parameter	Description	Required
`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 dsp@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. 205: The advertiser domain is filtered by the site settings. 1001: Missing cid in the DSP response. 1002: Creative requires supporting documents to pass moderation.	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"
    }
  ]
}
Copied to clipboard