Portfolio and reporting

The portfolio module calculates, per property and for the entire portfolio, rents, yields, cash flow after debt service, the occupancy rate, financial vacancy, the loan-to-value ratio and, for commercial leases, the weighted average lease term (WALT). These indicators are based on recorded leases, expenses and loans, ensuring consistency with day-to-day management.

See also: Property portfolio management, Estate agency dashboard

The owner report is produced in PDF format from the portfolio indicators, and you can download it or email it to the owner. It presents the status of the properties consistently from one owner to another, which facilitates discussions regarding the performance of their investments.

See also: Tenant, co-owner and buyer portals, Property portfolio management

The agency dashboard brings together indicators relating to mandates, sales lead times, viewings and fees. It is calculated from data recorded in the workstation, allowing management to monitor commercial activity without manual consolidation.

See also: Estate agency dashboard

The read-only REST API uses a key created by an organisation administrator, which is transmitted in the authorisation header as a bearer token. Only the fingerprint of the key is stored in the database, meaning that a lost key must be replaced rather than retrieved, and each key grants access solely to the data of its organisation.

See also: Integrations, Security and data protection

The platform webhooks transmit data as JSON POST requests and incorporate an HMAC-SHA256 cryptographic signature in their headers. This signature is calculated from a shared secret and the raw request body so that your server can verify the authenticity of each notification received. The service places these events in a dedicated queue to guarantee their delivery.

See also: Security and data protection, Integrations

Each key can perform up to 120 requests per minute, which protects the service for all clients. Results are paginated with a limit and a cursor, so large volumes can be retrieved in successive pages.

See also: Integrations

A response from your server outside the 2xx status codes is considered a failure, and transmission is retried during subsequent passes through the queue. After three unsuccessful attempts, the delivery is marked as failed, allowing you to identify the events that require processing on your end.

See also: Integrations