Validate Email Template Content
POST/api/store-email-templates/validate
Checks unsaved subject, preheader and body (or a brand layout) without saving.
settings:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Authentication: Requires Bearer token.
Body fields: template_id (optional, supplies the context), context, mode (template default, or layout), subject, preheader, html_body.
Errors (block a save): unknown_token (with suggestion and available_in), unbalanced_braces, unsafe_element, unsafe_attribute, unsafe_url, content_token_in_template, layout_content_token, body_too_long, subject_too_long, preheader_too_long.
Warnings (never block): subject_long, missing_preheader, own_page_wrapper, image_missing_alt, image_missing_width, button_without_fallback, unsupported_layout_css, unsupported_position_css, css_variables, external_stylesheet, insecure_link, gmail_clipping, low_contrast, single_brace_token.
Request
Responses
- 200
- 401
- 403
- 422
- 429
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
Validation failed — the body is a field → messages map (Laravel shape) or the platform envelope with a stable machine-readable code. Fix the payload and resubmit.
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.