A Yandex SDK Open Bidding response contains one SeatBid and one bid.

What it means

A Yandex SDK Open Bidding response contains one SeatBid and one bid. This check applies to the selected vendor contract and integration direction.

Why it matters

The declared profile checks the published partner contract alongside canonical OpenRTB. It does not verify runtime approval or account configuration.

How to fix it

Keep the value within the published boundary described above. Check Unicode character counts where the contract counts characters.

Example that trips it

{
  "id": "yandex-request",
  "cur": "USD",
  "seatbid": [
    {
      "bid": [
        {
          "id": "bid",
          "impid": "1",
          "price": 1,
          "ext": {
            "signaldata": "{\"cache_id\":\"opaque-ad\"}"
          }
        },
        {
          "id": "bid",
          "impid": "1",
          "price": 1,
          "ext": {
            "signaldata": "{\"cache_id\":\"opaque-ad\"}"
          }
        }
      ]
    }
  ]
}

Profile yandex-sdk-bidding, OpenRTB 2.5. The fixture asserts openrtb.profile.yandex.response_count at seatbid[0].bid.

Check your payload

Paste a bid request or response into the tester to see whether this code fires against it, or gate on the id in CI with the CLI: the id is stable, wording is not.

• Primary protocol documentation
• Replayable source fixture

Back to the full diagnostic code reference.