Create, bind and deliver each message code safely
-
1
Use a server application
High Security requires an approved server application with Gmail API authorization. A Gmail web, mobile or desktop signature can show only the Low Security linked seal image.
-
2
Build the final MIME identity
Create the complete RFC 2822 MIME message in the application and assign a unique Message-ID using the verified sender domain before calling VerifySeal.
-
3
Request and insert the code
Request the VEM code from the trusted server, add message_code.header to the MIME headers, and append the returned footer to every body alternative.
-
4
Send the raw MIME message
Base64url-encode the completed MIME message and submit it with the Gmail API messages.send method. Do not modify the body or identity after the VEM request.
-
5
Confirm Google preserved the identity
Retrieve or externally receive the sent message and inspect the original source. The final Message-ID must exactly match the value bound to the VEM code.
-
6
Check Workspace authentication
Confirm the received message has the VEM header/footer and aligned DKIM/DMARC passes. If Google replaces Message-ID in your flow, the integration is not compatible without a different gateway.