SIMID-1.0-simid-apiframework-case
apiFramework must be exactly "SIMID" (case-sensitive per SIMID §5)
Short answer
SIMID §5 requires apiFramework="SIMID" exactly. Near-miss values (simid, Simid, trailing space) are ignored by spec-compliant players. vastlint still runs the type and URL checks on those near-misses so the rest of the envelope is not skipped.
Why this matters in production
This is a compatibility warning. The creative may load in one player and behave inconsistently in another, especially across web and CTV implementations. Linear SIMID issues affect the handshake between the primary video creative and the interactive layer. When these break, the ad often falls back to plain video or fails interaction entirely.
SIMID §5 requires apiFramework="SIMID" exactly. Near-miss values (simid, Simid, trailing space) are ignored by spec-compliant players. vastlint still runs the type and URL checks on those near-misses so the rest of the envelope is not skipped.
How to fix
Set apiFramework="SIMID" with that exact casing. vastlint fix rewrites the common near-misses.
Broader troubleshooting
If this rule is one part of a bigger SIMID delivery issue, start with the SIMID troubleshooting guide for a checklist covering iframe URLs, HTTPS, fallback media, and player support. If the XML is already clean, test the live tag: a JS file, frame headers, or a missing createSession will not show up in the catalog.
Invalid
<InteractiveCreativeFile type="text/html" apiFramework="simid">
<![CDATA[https://example.com/creative.html]]>
</InteractiveCreativeFile>Valid
<InteractiveCreativeFile type="text/html" apiFramework="SIMID">
<![CDATA[https://example.com/creative.html]]>
</InteractiveCreativeFile>SIMID-1.0-simid-apiframework-case and other issues instantly.Open the VAST tag validator →