vastlint

VPAID-apiframework-casing

apiFramework value is not the canonical "VPAID" (wrong case)

WarningAttributesIAB VPAID 2.0 §3.1

The canonical value for VPAID is (all uppercase). Values like , , or are non-standard. Most desktop players do case-insensitive matching and will still initialise the unit, but some CTV and SSAI systems perform strict comparisons. Since VPAID is deprecated, the correct long-term fix is to migrate to SIMID rather than correct the casing.

Why this matters in production

Treat this as a migration and compatibility warning. VPAID issues often survive desktop QA and then fail silently on mobile, CTV, or SSAI paths. Attribute rules are where VPAID integrations break most often. The unit may be present, but a wrong type, casing, or dimension value prevents correct initialization.

How to fix

If staying on VPAID temporarily, change apiFramework to exactly "VPAID" (uppercase). The recommended path is to migrate the creative to SIMID.

Invalid

<MediaFile delivery="progressive" type="application/javascript"
           apiFramework="vpaid" width="1280" height="720">
  <![CDATA[https://example.com/vpaid.js]]>
</MediaFile>

Valid

<MediaFile delivery="progressive" type="application/javascript"
           apiFramework="VPAID" width="1280" height="720">
  <![CDATA[https://example.com/vpaid.js]]>
</MediaFile>
Check your VAST tag for VPAID-apiframework-casing and other issues instantly.Validate a tag →

Other Attributes rules

VPAID-type-invalidVPAID <MediaFile> type must be application/javascript or application/x-javascriptVPAID-width-height-missingVPAID <MediaFile> missing width or height attribute
← All VPAID rulesSIMID rules (migration target) →