Tenancies

Create Tenancy

Create one tenancy on a property, for a unit (unit_id from properties_units_list) and tenants who are already contacts (contact_ids from contacts_list or contacts_create, in lease order). A couple or a WG on one lease is one tenancy with every tenant in contact_ids, not one tenancy each. rent_net is the rent at the lease start; record later rent changes with tenancies_events_create. For many tenants from a rent roll use properties_rent_roll_apply. A retry with the same tenants, unit and start_date returns the existing tenancy (reused: true) unchanged; change it with tenancies_patch. Another tenancy on the same unit at the same time is not refused (a shared flat can hold two leases) but comes back in warnings as tenancy_overlaps: ask the user before you keep both, since both rents count.

RESTPOST /api/v1/properties/{id}/tenancies

Delete Tenancy

Delete a tenancy by id, for good, with its tenancy events. Use it for a tenancy that should never have existed (a duplicate, a wrong import). A lease that really ended is not deleted: set its end_date with tenancies_patch. The tenant contacts stay; a tenant link goes when no other tenancy backs it.

RESTDELETE /api/v1/tenancies/{id}

Record Tenancy Event

Record a dated change on a tenancy: a rent increase (Mieterhöhung, Staffel- or Indexstufe), a month without rent (Mietausfall), new operating costs, a new tenant prepayment, new separate management costs or new parking. From the month of date on, the cashflow and the key figures use value instead of the tenancy field; earlier months keep the old one. value is the new monthly amount, never the difference. Record the rent history as one event per change, oldest first is fine; an announced future increase is an event with its future date, never rent_net_target. date must lie within the lease. Repeating the same change returns the stored event; a different value for the same type and date is refused (event_exists): to correct one, tenancies_events_delete it first.

RESTPOST /api/v1/tenancies/{id}/events

Delete Tenancy Event

Delete one dated change of a tenancy (event_id from properties_units_list or properties_get). The cashflow is computed as if it never happened.

RESTDELETE /api/v1/tenancies/{id}/events/{eventId}

Update Tenancy

Update a tenancy by id (from properties_units_list or properties_tenancies_import); partial body. Correct start_date/end_date, rent_net, operating_costs (total, Hausgeld share) or operating_costs_transferable (tenant prepayment, Nebenkosten), set operating_costs_non_transferable (the share the owner carries per Wirtschaftsplan; null derives it as Hausgeld minus prepayment) and operating_costs_reserve (the WEG reserve inside that share, not tax-deductible yet), move it with unit_id, or replace the tenants with contact_ids (the whole list, in lease order; [] removes every tenant). Set end_date to record a lease that ended (Auszug, Räumung); end_date null reopens it. Dates are YYYY-MM-DD. rent_net is the rent from start_date on, for every month of the lease: a rent that changed later (Mieterhöhung, Staffel, Index) is never patched here, it is a dated change with tenancies_events_create.

RESTPATCH /api/v1/tenancies/{id}