What's newin LeonAI Signs.

Every change that reaches you, newest first, on the day it ships.

Releases in the last 30 days: 3. The latest: 31 October 2026.

  • Improved

    Swagger UI loads from LeonAI Signs itself.

The whole release

Releases

Improved

  • Swagger UI loads from LeonAI Signs itself. The interactive API explorer at /swagger used to fetch its code and styles from a third-party site; it now comes from LeonAI Signs, in a newer version (5.33.2, was 5.11.0). In dark mode its section headings, its table text and the operations' arrows and locks were too dark to read; they now show. On an agency's or organization's own domain, where the explorer never loaded, the links to it and to the OpenAPI file are gone, since both name LeonAI Signs. The API documentation page stays there, and /swagger opens it.

Improved

  • Search results now show the whole description of the pricing, industries, templates, comparison, trust and help center pages instead of cutting it off. The text on the pages themselves is unchanged.
  • SignFlow is now LeonAI Signs. The new name appears everywhere you read the product's name: the app, emails, the signing pages, signed PDFs and their audit trail, the public site, the terms and privacy pages, and the API reference. Nothing else changes: your account, templates, documents, API keys, webhooks and every link keep working at the same addresses. Documents signed before the change keep the name they were signed with. New charges are named LeonAI Signs; a running subscription's monthly charge keeps the old name until its plan or add-ons next change. A new two-factor sign-up shows LeonAI Signs in the authenticator app; one set up before keeps its name and keeps working.

Fixed

  • Fields on documents from Priority and other systems that draw the page at a scale land where the page shows them. Detection read the lines and tables of such a document at the wrong place. On a quote sent for signature it could make the letterhead's e-mail line, the footer, the title or an empty table column into a field the signer had to fill. Lines, tables and boxes are now read where they are drawn. An empty cell in a row of printed values is a value the document left out, not a blank. A round icon is no longer taken for a checkbox. This applies to documents uploaded or detected from now on; fields already saved don't change.
  • Typing "@" in a field's default value lists every field of the template. The list showed only the first 8 fields, so on a longer template the fields of later pages couldn't be chosen. Typing the start of a Hebrew label after the "@" now narrows the list ("@טלפ" finds "טלפון"), and picking a field writes its reference as before.
  • A signature line whose caption is printed under it is detected as a signature. When the caption ran over two lines ("חתימת הלקוח" / "על סעיף זה", or "הלקוח" / "(חותמת+חתימה)"), the line became a text field named after a single word of it, such as "סעיף". Detection now reads the caption whole: the field is a signature, named by its caption.
  • A detected checkbox sits on the document's own box. A checkbox found on the page got a large field above and to the side of the printed square, so the signed document showed a second, ticked box beside it. The field now covers the printed square, and the tick is drawn on it.
  • A detected field covers its whole blank line. A long blank, such as a name, an address or a signature line running half the page, got a box a quarter of the page wide in its middle, and the author had to widen it by hand. The box now runs from one end of the line to the other. A line that no caption of its own names, such as a divider, keeps the shorter box.
  • A detected field sits above its blank line, not across it. A box was set partly below its line, so in the signed PDF the line could run through the middle of a typed value on a crowded form, and a signature could hang over the text printed under its line. The box's bottom is now on the line. A one-line value's box is one line of text tall; signature, initials, text-area and image boxes keep their full height, all of it above the line.

New

  • Chat with us on WhatsApp from any page of the site. A green WhatsApp button in the corner of every public page (bottom left in Hebrew, bottom right in English) opens a chat with LeonAI's team in a new window, with a first message already written that says which page you came from. It shows only on signflow.leonai.io: an agency's own domain, the signing and preview pages and the app you sign in to don't have it.
  • The home page tells Priority users that SignFlow finds the signature on each document. Priority documents don't print the signature in the same place every time. The automatic field detection tile now says so, in Hebrew and English: send the document's own PDF through the API or the Make.com app, and SignFlow looks for the signature on that document instead of where the template put it.

Improved

  • Search engines that support IndexNow (Bing, Yandex, Seznam, Naver) are told about updated public pages right after each release, so changes show up in their results sooner.

Fixed

  • A mistyped or old address now opens a proper page. The app's own "not found" page was a bare "404". It is now the site's not-found page, in the site's design, in Hebrew or English: a plain sentence, the way back home, and the header and footer. Signed in, the header's button takes you back to the app. On an agency's own domain the page shows only the agency's name, never ours.
  • The not-found page speaks the address's language. A mistyped Hebrew address opened the new not-found page in English for a visitor who wasn't signed in. It now reads in Hebrew, right to left, and an address under /en/ in English, as the site's other pages do. Signed in, you keep your own language.
  • An address that doesn't exist on signflow.leonai.io now answers "not found" to search engines and AI tools. It used to answer like a real page, so a mistyped or old link could be listed in search results. You still see the same not-found page, in your language, with a way back to the home page. Every page of the app and every signing link opens as before.
  • AI verify in the API no longer replaces a template's fields. POST /api/v1/templates/{id}/ai-verify saved only the candidates sent to it and deleted every other field on the template. It now adds the ones it confirms beside the template's own fields, as AI suggest does, and never deletes or changes a field already there. Its response also lists the fields it added (added), and the API reference now describes the crops it reads.
  • Field detection reads drawn tables, underlined headings and dense forms correctly. When a PDF is uploaded or its fields are detected again, a heading's underline or a table's borders no longer become fields. The empty cells of a drawn table become fields, each named and typed by the header above it, such as a bank-account row under "בנק | סניף | סוג חשבון | מספר חשבון". On a form whose lines are close together, each field now fits its own line instead of covering the line above, and a signature keeps a little more room. Fields already on a template don't change.
  • A blank in the middle of a Hebrew sentence is now found where it is printed. When a line had a blank between words, such as a price followed by ₪ and VAT, field detection placed the box at the end of the line, so the value landed on the wrong words. The box now sits on the blank. This applies to documents uploaded or detected again; fields already on a template don't change.
  • On an agency's or organization's own domain, signers can pay by card and see the document as they fill it in, and the agency's users can sign in with Microsoft. The page's security policy there blocked the Pelecard and PayPlus card form, the document preview in the signing form, and Microsoft sign-in where the agency offers it. It now allows exactly those, and the card form can offer Apple Pay and Google Pay. It also blocks plugins and changes to the page's base address, as signflow.leonai.io does.
  • A price in the middle of a Hebrew sentence is named after what it prices. On a line such as "דמי שכירות חודשיים בסך ____ ₪", field detection now names the field "דמי שכירות חודשיים" instead of "Field". When the words before "בסך" don't say what the sum is for, the field keeps the name "Field", so a price never takes the name of an item printed beside it. This applies to documents uploaded or detected again; fields already on a template don't change.

Start with the latest