Skip to content

Document template · generic.facilities.sublease

Sublease Agreement

  • Render-verified
  • Legal-sensitive
  • Version 1.0.0

Sublease from an existing tenant (head tenant) to a subtenant. Country-agnostic. Subject to the head lease's consent rules (e.g. BE Loi 30.04.1951 art. 10 on commercial-lease subletting; FR Code de commerce art. L145-31; DE BGB paragraph 540).

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 34 fields:

Field Required Type Description
head_tenant Required object
head_lessor Required object Reference only; not a party to this sublease.
head_lessor.name Required string
head_lessor.address Required string
subtenant Required object
head_lease_reference Required object
head_lease_reference.date Required date
head_lease_reference.ref Required string
premises Required object
premises.portion_leased_description Required string
premises.floor_area_sqm Required number
premises.floor_plan_ref Optional string
sub_term Required object Must fit strictly inside the head lease term.
sub_term.start Required date
sub_term.end Required date
sub_rent Required object
sub_rent.amount_monthly Required number
sub_rent.currency Required string
sub_rent.payment_day Required integer
sub_rent.security_deposit Optional number
head_lessor_consent Required object
head_lessor_consent.obtained Required boolean
head_lessor_consent.date Optional date
head_lessor_consent.consent_letter_reference Optional string
allocation_of_obligations Required object
allocation_of_obligations.utilities Required string
allocation_of_obligations.maintenance Required string
allocation_of_obligations.insurance Required string
termination_provisions Required string
signatures Required object

+4 more fields — the full JSON Schema is available in the dashboard and via the API.

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
curl -X POST https://api.papii.eu/render \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "template": "generic.facilities.sublease",
    "data": { ... },
    "options": {"language": "en"}
  }' -o sublease.pdf

Frequently asked questions

What is “Sublease Agreement”?

Sublease from an existing tenant (head tenant) to a subtenant. Country-agnostic. Subject to the head lease's consent rules (e.g. BE Loi 30.04.1951 art. 10 on commercial-lease subletting; FR Code de commerce art. L145-31; DE BGB paragraph 540). On papii this document is available as template generic.facilities.sublease: a JSON Schema plus a deterministic PDF renderer, so the same data always produces the same document.

Can I generate a Sublease Agreement 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 Sublease Agreement 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.