Email Template Package QC

Check a synthetic email template package for supported MIME structure, content-ID references and literal merge-field coverage. Receive one complete machine-readable report containing parts, references, field occurrences, findings, summary counts and input/report hashes.

USD 0.10 per completed report, including platform usage. A completed report can contain errors or warnings: completion means the supported checks finished, not that the template passed. Unsupported or incomplete packages do not produce a completed-report dataset item. If a run stops after its dataset append was attempted, delivery and billing may be uncertain; inspect the dataset and run details before considering another run.

Try the demo

Use the default input:

{"useDemo":true}

The included synthetic package exercises the checks without supplying your own data. Omit templateBundleJson. Leave authorizedNonpersonalNonconfidentialData absent or false in demo mode.

Check your own synthetic package

Set useDemo to false and authorizedNonpersonalNonconfidentialData to true. Supply templateBundleJson as a string containing the exact native JSON bundle. The two native attestations are also required; the service does not inject them.

{
  "useDemo": false,
  "authorizedNonpersonalNonconfidentialData": true,
  "templateBundleJson": "{\"schemaVersion\":\"n32-input/1\",\"syntheticTemplateOnly\":true,\"authorizedToProcess\":true,\"template\":\"MIME-Version:1.0\\r\\nContent-Type:text/plain;charset=utf-8\\r\\n\\r\\nHello {{name}}\",\"namedFields\":[\"name\"]}"
}

Only submit authorized, nonpersonal, nonconfidential synthetic data. Do not submit real messages, customer contact lists, credentials or private business content. Apify stores the input before execution. These attestations do not anonymize data or detect every secret or personal identifier. The service performs no network retrieval, inbox access or email sending.

Preserve CRLF line endings inside the template using JSON escapes. Do not add a byte-order mark, extra envelope fields, duplicate JSON keys or remote URLs in place of the bundle. templateBundleJson is at most 2,200,000 UTF-8 bytes; the outer input is at most 4,500,000 bytes. The MIME template is at most 1 MiB, with at most 50 parts, depth 8, 100 declared fields, 1,000 CID references and 1 MiB total decoded payload. Runtime checks enforce byte and structure limits.

Get the complete report

Open the output dataset and download the raw full JSON items. The table is a preview; reportJson contains the entire native report as a JSON string. Do not copy a truncated table cell or select a shortened subset of fields.

For a local JSON download named dataset.json, this Python 3 snippet verifies the exact report bytes and saves report.json:

import hashlib, json
from pathlib import Path
items = json.loads(Path("dataset.json").read_text(encoding="utf-8"))
assert isinstance(items, list) and len(items) == 1
item = items[0]
raw = item["reportJson"].encode("utf-8")
assert len(raw) == item["reportBytes"]
assert hashlib.sha256(raw).hexdigest() == item["reportSha256"]
report = json.loads(raw)
assert report["status"] == "complete"
assert report["eligibleForCompleteReport"] is True
Path("report.json").write_bytes(raw)

Keep the deliveryKey, reportSha256 and receipt with the report. Hash checks detect accidental corruption; they do not establish source authenticity or payment settlement. Receipt settlementStatus=not_verified and native pricing/charged fields are report metadata, not a billing ledger. Check the platform run details for actual billing.

What the checks cover

The narrow supported profile covers text/plain and text/html bodies, supported image attachments, selected multipart structures, 7bit/8bit/base64/quoted-printable decoding, message-global case-sensitive CID matching and literal {{field}} tokens. Findings include missing or ambiguous CID targets, undeclared or missing fields, plain/HTML coverage differences and empty text bodies. Complete reports can contain findings that require attention.

This is not full MIME or HTML standards validation, email rendering, inbox placement testing, deliverability certification, malware scanning, archive extraction, attachment execution or rights verification. It does not evaluate template expressions or guarantee that alternate parts render alike. Unsupported MIME, HTML, charset, encoding or merge syntax may make a package incomplete. Input and output are bounded; no automatic repost or retry occurs after an uncertain append.