Postcard Studio

Postcard Studio is PostPal's built-in design editor. Instead of uploading a finished print file, you design your postcard directly in the browser.

What you design in the Studio:

• Text fields & background of the postcard. Text fields can contain static text and optional variables such as {{first_name}}.
• API Markdown for API flows, with content supplied per recipient through the API. Designs with Markdown areas are not available for regular campaigns.
• QR codes as URL QRs or API QRs. URL QRs store their target URL in the design; API QRs define API field names whose values are supplied per API request through qr_codes.
• Lines and simple layout elements.

Your uploaded design remains unchanged. Use Text only to add content that appears over the design or changes per recipient.

The Studio is format-aware: it knows bleed, address zone and whether a format is two-sided, and checks your layout against the print requirements. This keeps elements out of invalid zones and keeps your design printable. You can still upload a finished print file instead.

API Markdown shows stored example content in the editor. This example text is only for layout and preview; it is not used as fallback content for real API mailings. The actual Markdown content must be submitted through the matching API content key. Studio variables such as {{first_name}} are not allowed inside Markdown areas.

When adding a QR code, you choose between URL QR and API QR. A URL QR is for CSV, Klaviyo, fixed links or URL templates; its target URL lives in the design and can contain known placeholders such as {{voucher_code_1}}. An API QR is for API flows. It receives its own API field name, and the placeholder for that field name becomes the exact QR content, for example {{voucher_url_1}}. The actual value is later submitted per recipient through the matching API qr_codes key and must be a complete HTTP(S) URL. Multiple newly inserted API QRs are numbered automatically in the Studio, for example voucher_url_1, voucher_url_2.

When your design contains API Markdown areas or API QRs, use API-Beispiel in the Studio to generate a current example payload and matching cURL request. The output uses the API field names and Markdown example content from the current editor state. The flow ID, API token and idempotency key are deliberate placeholders. URL QRs and other non-API-bound elements are not emitted as dynamic API fields.