> ## Documentation Index
> Fetch the complete documentation index at: https://docs.trassets.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# v1 Depreciation Data Model: Assets

> Field-level reference for the v1 Depreciation table assets, including the afa_period object and the asset_id/asset_number pair.

The v1 Depreciation domain covers one table: `assets`, which follows the [response
structure](/v1/response-shape-conventions) rules.

<Note>
  The `depreciation` postings table has no `/v1/` endpoint yet — fetch it via
  [`Depreciation.depreciation`](/data-model/depreciation#depreciation) in the meantime. Until
  then, a full depreciation schedule for an asset can't be assembled from `/v1/` alone.
</Note>

## assets

`GET /v1/depreciation/assets` — fixed-asset master data.

<ResponseField name="property_id" type="string" required>
  Unique property identifier.
</ResponseField>

<ResponseField name="asset_id" type="integer" required>
  Internal asset identifier — the same `*_id` / `*_number` split as
  `Accounting.accounts.account_id`/`account_number`.
</ResponseField>

<ResponseField name="asset_number" type="string">
  Human-readable asset number.
</ResponseField>

<ResponseField name="asset_name" type="string">
  Asset name.
</ResponseField>

<ResponseField name="acquisition_date" type="date">
  Date the asset was acquired.
</ResponseField>

<ResponseField name="built_date" type="date">
  Date the asset was put into service.
</ResponseField>

<ResponseField name="afa_period" type="object">
  Depreciation schedule — `{start, end}` (date strings).
</ResponseField>

<ResponseField name="depreciation_active" type="boolean">
  Whether depreciation is currently active for this asset.
</ResponseField>

<ResponseField name="afa_duration" type="string">
  Depreciation duration in years, as a string (e.g. `"50"`).
</ResponseField>

<ResponseField name="afa_method" type="string">
  Depreciation method applied.
</ResponseField>

<ResponseField name="afa_validity" type="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.
</ResponseField>

<ResponseField name="afa_group" type="string">
  Depreciation category the asset belongs to (e.g. `"Gebäude"`, `"Garagen"`).
</ResponseField>

<ResponseField name="afa_buch_id" type="string">
  Undocumented. Contact support before relying on it.
</ResponseField>

<ResponseField name="account_name" type="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.
</ResponseField>