Highlights
- Send a picture with your answers to a document template, as a base64 string in the same request.
- Dates sent to a document template are read one way, and a date like 07/10/2026 is refused with a message saying why.
- A workflow's draft step stops and names the field rather than print a date that could mean two different days.
A small update to the API and document drafting. Document templates now take pictures, and a single date format is now accepted.
What's new
- API. An image field on a document template now takes a picture in the request, with the rest of the answers, as a base64 string, with or without a
data:prefix: PNG or JPEG, up to 1 MB and 2,000 pixels on each side. A picture that doesn't fit is refused with its field named, like any other answer. Leave it out and the workspace's picture prints, if the field has one. A picture your workspace sets for every document, such as a letterhead logo, still can't be replaced. See document templates.
Changes to be aware of
- API. Dates sent to a document template are now read one way:
yyyy-MM-dd, a date-time, or a date with the month written as a word. Any other numeric date is now refused with a message saying why, rather than read month-first:07/10/2026is 7 October in some systems and 10 July in others. Convert your system's dates before you send them. - API. A template's input schema now describes an image field as a base64 string, and a request to produce a document can be up to 10 MB.
- Ferrith Chat. The same reading applies across document drafting: a workflow's draft step given a date that could mean two different days now stops and names the field, rather than print the wrong day.
Fixed
- A date-time sent to a document template now keeps the day it was written for. Its time zone could move it by a day.