Postcard-design requirement
An API flow supplies recipients and trigger logic, but the postcard itself comes from a design. That is why every flow must reference a valid postcard design. You can create the design in the Design Editor or upload a finished print file.
Every API flow needs a postcard design. The flow decides which recipients arrive through the API and when they are processed. The design decides what gets printed.
You can use:
- a design created in the Design Editor,
- or a finished print file added through design upload.
Without a valid design, PostPal cannot turn flow entries into a printable mailing batch.
Fonts: TTF, OTF, WOFF and WOFF2 are prepared for print automatically. The Design Editor and PDF output use the same prepared font. Original files are preserved. Corrupt or unconvertible files prevent binding the design to a flow; the error names the affected fonts. Upload another version in that case. Individual font files may be up to 20 MB. Variable fonts use their default axis values.
When creating a design while setting up a flow, you can choose formats offered by the published catalog and supported by the studio. Format names also come from that catalog.
Frequently asked questions
Why does an API flow need a design?
The flow collects recipients, but PostPal needs to know which card to print. That requires a linked postcard design.
Can I use a design from the Design Editor?
Yes. API flows can use designs from the Design Editor or uploaded print files.
What happens without a design?
Without a valid design, PostPal cannot create a printable mailing batch.
Which fonts can I use in an API-flow design?
TTF, OTF, WOFF and WOFF2. PostPal automatically prepares these formats for print. The Design Editor and PDF output use the same prepared font. Corrupt or unconvertible files produce an error; upload another version of the font. Individual font files may be up to 20 MB. Variable fonts use their default instance.