assets, which follows the response
structure rules.
The
depreciation postings table has no /v1/ endpoint yet — fetch it via
Depreciation.depreciation in the meantime. Until
then, a full depreciation schedule for an asset can’t be assembled from /v1/ alone.assets
GET /v1/depreciation/assets — fixed-asset master data.
string
required
Unique property identifier.
integer
required
Internal asset identifier — the same
*_id / *_number split as
Accounting.accounts.account_id/account_number.string
Human-readable asset number.
string
Asset name.
date
Date the asset was acquired.
date
Date the asset was put into service.
object
Depreciation schedule —
{start, end} (date strings).boolean
Whether depreciation is currently active for this asset.
string
Depreciation duration in years, as a string (e.g.
"50").string
Depreciation method applied.
string
Date the depreciation method became valid, formatted
DD.MM.YYYY (e.g. "01.05.2019") —
not ISO-8601 like the other date fields on this table. Don’t parse it the same way.string
Depreciation category the asset belongs to (e.g.
"Gebäude", "Garagen").string
Undocumented. Contact support before relying on it.
string
Accounting basis this depreciation record is booked under (e.g.
"Handelsrecht",
"Steuerrecht") — German GAAP vs. tax law depreciation can differ for the same asset.