Version 1

The current version of Ledgerlot covers the full path from drafting a document to getting it signed and organized — not just the first draft.

• Guided document builders for a combined business + real estate purchase LOI, a commercial lease LOI, and a New Brunswick residential lease — live preview as you fill out the form.
• Upload any of your own PDF forms and anchor its fields once — it becomes a reusable template for every future deal, with signature/date/text fields auto-detected on real AcroForms.
• Sequential e-signature with enforced signer order, decline/expiry handling, reminder emails, and a tamper-evident, hash-verified audit trail with a Certificate of Completion.
• Sign your own document immediately in-app if you added yourself as a signer, or send it and sign later from the emailed link — your choice.
• A document locks against edits once it's out for signature, so a signer never reviews terms that quietly changed underneath them — void the request first to make changes.
• Folder-based deal pipeline with Draft/Active/Pending/Closed stages on a Kanban board, tasks, threaded comments, and a unified activity feed.
• Granular sharing — grant access to a whole deal folder, or to just one document within it.
• Business accounts get org-wide branding on outgoing emails, an included REST API, and webhooks for CRM/automation integrations.
• Sign in with an emailed magic link, or set a password for faster returning sign-in — your choice, and the link always keeps working either way.
• Document retention: 30 days fixed for personal accounts; business accounts get 1 year up to Lifetime depending on plan size, extendable further on request.
• Business account verification for organizations that need it, reviewed by an admin.
• Light and dark mode, applied across the whole app.

API Reference

Business accounts get a REST API for integrating Ledgerlot with a CRM (Lone Wolf, kvCORE, Follow Up Boss, or your own tooling) — create documents from a template, send them for signature, poll status, and download the executed PDF and Certificate of Completion. Every endpoint is Bearer (API key) authenticated and scoped to your org; keys are managed under Org Settings → API Keys.

Full machine-readable schema: /v1/openapi.json (OpenAPI 3.1).

• GET /api/v1/folders — list folders
• GET /api/v1/folders/{id}/documents — list documents in a folder
• POST /api/v1/folders/{id}/documents — create a built-in document (LOI/lease) in a folder
• GET /api/v1/documents/{id} — get a document and its latest signature status
• GET /api/v1/templates — list templates available to create documents from
• POST /api/v1/templates/{id}/documents — create a document from a template, filled from a flat answers object
• POST /api/v1/documents/{id}/signature-requests — send a document for signature
• GET /api/v1/signature-requests/{id} — poll status: pending / fully_executed / voided / declined, per signer
• POST /api/v1/signature-requests/{id}/void — cancel an in-progress signature request
• POST /api/v1/signature-requests/{id}/remind — resend the signing-link email
• GET /api/v1/signature-requests/{id}/pdf — download the final executed PDF
• GET /api/v1/signature-requests/{id}/certificate — download the Certificate of Completion

POST /api/v1/templates/{id}/documents and POST /api/v1/documents/{id}/signature-requests support an optional Idempotency-Key request header — retrying with the same key returns the original response instead of creating a duplicate document or sending duplicate signature invites.