ImmobiNet
ImmobiNet API Docs - Transactions

ImmobiNet API Docs - Transactions

PMS ImmobiNet - Transactions, the cash movements of the agency (read only).

Visibility: the API requires the privilege that gives access to the cash movements list in the application (cassa) and returns the movements of that list that belong to the agencies the API user belongs to (has a role in); movements without an agency are never returned. When the API user has a webservice configuration, only the movements of the properties enabled for that configuration are returned (also the property of the linked reservation must be enabled); movements without a property are not returned. The customer is given only as contact_id: the personal data are in /api/v1/contacts, with their own visibility rules. When the customer is anonymised for the API user, notes is null, because free text can contain names.

Period: date_from and date_to filter on the movement date (both inclusive), as the period filter of the application. Without them all movements are returned.

No updated_since: transactions have no modification date, so they cannot be polled for changes. Items are ordered by created_at (registration time), then by id. _pagination.next_cursor only moves through the pages of one read: it is null on the last page, so it cannot be kept to resume later, and there is no filter by id or created_at. To find new movements, read the list again from the first page, narrowed with date_from (e.g. a few days before the last run, since a movement can be registered with a past date), and skip the ids you have already processed. Do not stop at the newest created_at you have seen: it is set when the movement is saved, slightly before it becomes visible, so a movement can appear later with an older created_at. Changes to existing movements and deletions are not visible through polling.

Amounts: amounts are decimal numbers in euro (not in cents). amount is always positive: whether the movement is an income or an expense is the direction of its type, in GET /api/v1/transaction-types.

Types and payment accounts: a movement carries only the code of its type and of its payment_account; names, groups and the direction of each type are read once from GET /api/v1/transaction-types and GET /api/v1/transaction-payment-accounts. Types are shared by the whole installation; payment accounts are returned only for the agencies the API user belongs to.

Optional fields: fields that are not available to every installation (invoice_id and receipt) are always present and null when not available or without a value. custom_fields is always present. Custom fields are not available for transactions yet, so it is an empty object.

Timezone: all date-time values are in the Europe/Rome timezone (RFC 3339 with explicit offset, e.g. 2026-06-26T14:30:00+02:00).

Security Schemes
basicAuth
HTTP basic
http