Request-stage call carries a bid response

What it means

The envelope declares the publisher bid request stage and also carries a bid response. At that stage no DSP has answered yet, so there should be nothing to carry.

Why it matters

Either the stage is mislabelled or the envelope is being reused across stages, and both mean the agent's view of where it sits in the auction is wrong. It is a warning rather than an error because a private arrangement to pass prior-auction context is conceivable, and this validator will not invent a prohibition the specification does not state.

How to fix it

Set the stage that matches what you sent. If you are passing historical context deliberately, put it in ext rather than in the bid_response member.

Example that trips it

{ "id": "ep-1", "tmax": 120, "lifecycle": "LIFECYCLE_PUBLISHER_BID_REQUEST", "bid_request": { "id": "a-1" }, "bid_response": { "id": "a-1" } }

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.

Back to the full diagnostic code reference.