Documentation Index
Fetch the complete documentation index at: /llms.txt
Use this file to discover all available pages before exploring further.
Reference guide to common field names across the Trassets Data API, including entrance, address, floor_area_id, property_id, and pagination cursors.
| Field | Type | Description |
|---|---|---|
entrance | string | Street name and house number, e.g. Musterstrasse 12 |
address | string | Comma-separated postal code and city, e.g. 10115, Berlin |
name | string | Full name as a single field. No separate first or last name is available. |
floor_area_id | string | References floor_area_id in the property_structure table |
property_id | integer | Unique property identifier; primary join key across all domains |
person_id | string | Identifies a tenant or contact person |
creditor_id | string | Identifies a creditor (vendor or service provider) |
booking_date | date | ISO-8601 date of the ledger booking |
next_cursor | string | Opaque cursor for Raw endpoint pagination; null when all rows are fetched |
join_key | string | Bridge key produced by property_structure; equals account_id for cost-centre nodes or floor_area_id for floor-area nodes. Used to join bookings and tenancy data to a specific unit or cost centre. |
floor_area_person_id | integer | Composite key identifying a specific tenant in a specific unit. Appears in Contracts.contract_debits and Contracts.contract_ends. |
property_id_person_id | integer | Composite key identifying a specific tenant at property level, without unit granularity. Appears in Contracts.contract_debits and Contracts.contract_debit_diffs. |
account_id | string | Ledger account reference. Links Contracts debit records to Accounting. |
contract_id | integer | Contract identifier. Appears in Contracts.service_contracts and related contract records. |
controct_prolongation_months | integer | Extension length in months, in Contracts.contract_ends. The field name reflects a spelling irregularity in the underlying source system (controct, not contract) — not a typo in this documentation. |
sk_ are internal surrogate keys used for joins in the underlying data warehouse. They are not stable identifiers for external use and should not be relied on in your integrations.