Rule reference

Field required by the declared exchange profile

openrtb.profile.field_requirederrorBid request

An exchange profile was declared, and a field that exchange documents as required is missing or empty.

What it means

The selected exchange and integration direction document a mandatory field or a conditional requirement satisfied by this capture. Examples include Google Imp.ext.billing_id, supplied Prebid stored-request IDs, BidSwitch billing URLs, and supplier routing identifiers. Optional Xandr identity/context fields and Magnite xAPI protobuf fields are checked when provided. Their omission is not universally rejected.

Why it matters

A partner contract can require information beyond canonical OpenRTB. Direction matters: supplier ingest requirements do not automatically apply to bidder traffic. Mandatory errors use published requirements; unresolved account configuration remains outside capture-only validation.

How to fix it

Populate the field the profile names, or drop --profile / profile if you meant the specification only. Floors, blocklists, and other business policy are not encoded here.

Example that trips it

{ "id": "req-1", "imp": [{ "id": "1", "banner": { "w": 300, "h": 250 } }] }

Validated with --profile google-ab. The same payload is valid against the specification, which does not require Imp.ext.billing_id.

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.