Document template · generic.legal.loi
Letter of Intent
- Render-verified
- Legal-sensitive
- Version 1.0.0
Letter of Intent (LOI) — typically mostly non-binding statement of a commercial deal's main terms, used to frame due diligence and negotiation of a definitive agreement. Usually binding only as to selected provisions (exclusivity, confidentiality, costs, governing law).
JSON Schema
Fields in this template
Data sent to the API is validated against the template’s JSON Schema before anything is rendered. This template defines 26 fields:
| Field | Required | Type | Description |
|---|---|---|---|
| reference | Optional | string | |
| parties | Required | array of object | |
| parties[].role | Required | string | E.g. 'Buyer', 'Seller', 'Lessee', 'Lessor', 'Investor', 'Target'. |
| parties[].legal_name | Required | string | |
| parties[].address | Required | string | |
| parties[].registration_number | Optional | string | |
| parties[].representative_name | Required | string | |
| parties[].representative_role | Optional | string | |
| date | Required | date | |
| subject_matter | Required | string | Plain-language description of the transaction being contemplated. |
| key_commercial_terms | Required | string | Price, structure, indicative timeline, conditions — prose. |
| exclusivity_period_optional | Optional | object | |
| exclusivity_period_optional.days | Required | integer | |
| exclusivity_period_optional.scope | Required | string | Whose solicitations are restricted, and over what activities. |
| due_diligence_period_optional | Optional | object | |
| due_diligence_period_optional.days | Required | integer | |
| due_diligence_period_optional.access_terms_summary | Required | string | How the investigating party accesses the other party's information, the data-room logistics, and what cooperation is required. |
| definitive_agreement_target_date | Required | date | |
| binding_provisions | Required | array of string | |
| non_binding_disclaimer | Required | string | Explicit statement that, save for the listed binding provisions, the LOI does not create an obligation to conclude the transaction. |
| signatories | Required | array of object | |
| signatories[].party_legal_name | Required | string | |
| signatories[].name | Required | string | |
| signatories[].role | Required | string | |
| signatories[].date | Optional | date | |
| signatories[].place | Optional | string |
POST /render
Generate it
One POST /render call: send your JSON, get the finished PDF back. Or skip the JSON entirely and describe the document in plain language on chut.app.
curl -X POST https://api.papii.eu/render \
-H "X-API-Key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"template": "generic.legal.loi",
"data": { ... },
"options": {"language": "en"}
}' -o loi.pdf Frequently asked questions
What is “Letter of Intent”?
Letter of Intent (LOI) — typically mostly non-binding statement of a commercial deal's main terms, used to frame due diligence and negotiation of a definitive agreement. Usually binding only as to selected provisions (exclusivity, confidentiality, costs, governing law). On papii this document is available as template generic.legal.loi: a JSON Schema plus a deterministic PDF renderer, so the same data always produces the same document.
Can I generate a Letter of Intent with AI?
Yes. chut.app — the AI back office papii powers — fills this template from a plain-language description: you describe the document in one sentence, the AI structures the data, papii validates it against the schema and renders the PDF. Developers can also call the papii API directly with structured JSON.
Is the Letter of Intent template legally compliant?
This template is render-verified: its schema, sample data and PDF output are automatically tested on every release. It is published with status “ready”, meaning it has not yet been through papii’s final legal review. Where it references specific legislation, that is stated in the template description — always have a professional check documents with legal effect before relying on them.