Loss reason notifications

You can pass a dynamic lurl via the seatbid.bid.lurl field of the DSP response. You can also set up a dedicated URL for your DSP to receive loss reasons via the POST method in JSON format (Content-Type: application/json). If you want to enable this feature, contact your manager or email us 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, where each object represents a single bid.

Yes

Notifications object

crid

ID of the creative.

Yes

requestid

Auction ID assigned by the RTB host.

Yes

impressionid

ID of the ad unit on the HTML page.

No

status

Reason for bid rejection. Possible values:

  • 0: Winning bid.
  • 1: Internal error. For details, contact your manager or newpartners@yandex-team.ru.
  • 3: Invalid JSON in the DSP response.
  • 9: Invalid or missing bid price.
  • 102: Lost bid.
  • 200: Creative rejected for unknown reasons.
  • 201: Creative is pending moderation.
  • 202: Creative failed moderation.
  • 203: Creative dimensions (w/h) in response don't match the dimensions specified in the request.
  • 204: Invalid creative format.
  • 205: The advertiser's domain was filtered out by the publisher's settings.
  • 209: Creative's category blocked by the publisher's settings.
  • 1001: Missing cid in the DSP response.
  • 1002: Creative requires supporting documents to pass moderation.
  • 1111: The Open Bidding auction was lost.
  • 1347: ERID is missing in the response. This only applies to impressions served in Russia. For more information, see the documentation.
  • 1413: Adm payload exceeds the maximum allowed limit.

Yes

reasons

Reasons for failing moderation. You can view the specific error code using a link like https://yandex.ru/support/direct-tooltips/modadvert-XXX.html, where XXX is the value passed in the reasons field.

Yes, if the status code is 202

payload

Custom string retrieved 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"
    }
  ]
}
Previous
Formats and mechanics
Next
App