Financial resources and reference data
Assets, liabilities, incomes and expenses are separate resources connected to client information. Their categories and types are reference data, and ownership or linked-resource relationships carry meaning that is not captured by a flat list of values.
Preserve the relationships
An asset is not the same resource as a deal security. An income may have a linked asset. Financial information can be associated with people or a shared contact-group context. Use the exact relationships supplied by the API rather than inferring ownership from a display name.
Interpret fields carefully
Read each property's schema for data type, nullable values, units, frequency and currency where supplied. Zero, null and an omitted value can mean different things. Do not infer that a value is monthly or annual unless the field contract or associated frequency says so.
Use categories, types and subtypes from their reference endpoints. Labels may change; retain identifiers for mappings and refresh lookup data on a deliberate schedule.
Available operations
Readability does not imply writability. Use only the methods listed for the resource in the reference. New financial-write capabilities may be introduced separately and may carry a Beta label; this guide does not promise access to unpublished endpoints.
For efficient extraction, see rate limits and synchronisation.