Extract the sender, recipient, date, subject, body, and threading references from a business letter or memo PDF. No signup, no email required.
The full guide: Business letter and memo format, read as fields
Need to scale? Create an API key, then run this from your own code or an agent.
Create an API keyFree account required
Upload a file or pick a sample, and see the fields come back.
No signup · nothing stored
The document type (enum, letter or memo), the document number, the document and effective dates, the sender name, title, department, and contact info, the recipient name, title, organization, and address, and the CC and reply-to lines.
Yes. The subject line, the salutation, a body summary and the full body content, the closing statement, and the signatory each come back as their own field, so the letter message is captured as structured text.
When the letter or memo carries them, the message ID, the in-reply-to reference, and the references chain come back as fields, alongside the from and to lines and the document language, so a converted email thread keeps its threading metadata.
The document type field records whether the item is a letter or an internal memo; both share the same sender, recipient, subject, and body fields, so the extractor returns the same structure either way and you read the document type field to tell them apart.
PDF only, up to 10MB and 100 pages. The document is processed via the Talonic API for extraction, is not retained for training, and is not shared.
The tool reads a single document. The platform reads the whole estate once and keeps it queryable — the same engine, with a memory.
See PDF to Markdown if you run this for data and platform teams, or the extraction API if you are building it in.