{} has no verified OpenRTB {} {} contract in this build. Canonical specification checks were applied.

What it means

{} has no verified OpenRTB {} {} contract in this build. Canonical specification checks were applied. 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

Choose a profile with a verified contract for this payload direction and OpenRTB family. Specification validation remains available.

Example that trips it

{
  "id": "req",
  "device": {
    "ua": "browser",
    "ip": "192.0.2.1"
  },
  "user": {},
  "site": {
    "domain": "publisher.example"
  },
  "imp": [
    {
      "id": "1",
      "banner": {
        "w": 300,
        "h": 250
      }
    }
  ]
}

Profile applovin-alx, OpenRTB 2.6-202606. The fixture asserts openrtb.profile.scope.unsupported.

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.