/bff/emailer/download-confirmation

Generates a print-ready A4 PDF that serves as an evidentiary record of a sent e-mail. The certificate contains: internal message ID, SMTP Message-ID, current status, all key timestamps (created, sent, earliest scheduled, next retry), failed-attempt counter, message locale, open tracking, participants (from / to / cc / bcc / reply-to), the full system log, every recorded delivery event (bounces, SMTP rejections), the attachment list, and the exact HTML body handed to SMTP. Returned inline so the browser previews it in a new tab; not persisted to blob storage.

EmailergetBffEmailerDownload-confirmation

Parameters

2 query

Query parameters

· 2

emailIdstringRequired

Email message external ID to certify.

Exampleabc123

localestringOptional

Communication locale code — controls the language of textual data (product names, descriptions, articles, storefront UI, transactional e-mails).

Preferred format: BCP 47 language tag — language[-Script][-REGION]. Use the full tag whenever the script or region matters:

en-GB vs. en-US (British vs. American spelling)
pt-PT vs. pt-BR (European vs. Brazilian Portuguese)
zh-Hans vs. zh-Hant (Simplified vs. Traditional Chinese)
sr-Latn vs. sr-Cyrl (Latin vs. Cyrillic Serbian)

Backwards-compatible fallback: the bare two-letter ISO 639-1 code (cs, en, pl, …) is accepted indefinitely — legacy clients that only send the language subtag continue to work unchanged.

Resolution algorithm (server-side): the input is resolved against the supported locale list via the [RFC 4647 Lookup] progressive-fallback strategy — trailing subtags are stripped one by one until a supported locale is found. Example: en-GB-oxendict → en-GB → en (matched). If no subtag combination is supported, the request is rejected.

Currently supported locales: cs, en, fr, it, pl, de, sk, sv, es, zh, ja, uk, da, hu, ro, nl, pt, fi, nb, hr. Region-specific variants (e.g. en-GB, pt-BR) are accepted and resolved to their base language when the exact variant is not registered separately.

Length: 2–35

Examplecs

Response schema

1 status code documented

200Success

This response returns no JSON body.

Response example

application/json

{
  "success": true
}

Request example

GET /bff/emailer/download-confirmation

get

curl -X GET "https://api.bizkithub.com/bff/emailer/download-confirmation?emailId=abc123&locale=cs" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_KEY"

Need an API key?

All BizKitHub public API endpoints require authentication via API key.

Get API Key