Skip to main content
The two tables below join to each other and to the Property domain. See the Data Model Overview for the complete cross-domain diagram.

assets

GET /v1/depreciation/assets — fixed-asset master data, including the depreciation configuration applied to each asset.
string
required
Unique property identifier.
integer
required
Internal asset identifier. Referenced by depreciation.asset_id.
date
Date the asset was acquired.
date
Date the asset was put into service.
object
Start and end date of the asset’s own depreciation schedule.
boolean
Whether depreciation is currently active for this asset.
string
Asset name.
string
Useful life of the asset, in months.
string
Validity date of the depreciation-rate configuration applied to this asset. In practice, always identical to depreciation_period.start — an ETL duplicate, not an independent signal. Scheduled for removal in a future API version.
string
Depreciation method applied, as a label (e.g. straight-line).
string
Identifier of the depreciation account this asset’s postings are booked to.
string
Asset posting group this asset is classified under.
string
Name of the depreciation account this asset’s postings are booked to.
string
Asset number (business identifier), distinct from asset_id.

depreciation

GET /v1/depreciation/depreciation — individual depreciation postings, one row per booking.
string
required
Unique property identifier.
integer
required
References the asset this posting writes down. Joins to assets.asset_id.
date
required
Date of the depreciation posting.
number
required
Net value posted in this depreciation entry.
string
Free-text description of the posting.
string
Asset number (business identifier), matches the same field on assets.
One assets row typically has many depreciation rows over its useful life — join on asset_id to build a full depreciation schedule for an asset.