# Retrieve a depreciation schedule

Operation ID: `getDepreciationSchedule`

Group: Accounting › Fixed Assets › Depreciation Schedules

[Open in the interactive reference](https://docs.api.lensing.ai/lensing/v1/endpoints/getDepreciationSchedule)

`GET /fixed-assets/depreciation-schedules/{id}`

Read-only: Reads and returns; changes nothing.

Retrieves a depreciation schedule. To find a schedule by its schedule number, use `POST fixed-assets/depreciation-schedules/search`.

## Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `Api-Version` | header | string · v1 | yes | The API version this request targets, named by its public identifier. Required on every request; omitting it, or naming a version this company does not have, is answered with 400. This document describes version `v1`. |
| `id` | path | string | yes | The unique identifier of the depreciation schedule you want to retrieve. |

## Response

`200` Success

Under `data` (getDepreciationScheduleOutput):

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `id` | string | yes | The unique identifier for the depreciation schedule. Example: `"7c2e5a91-3f84-4b60-9d17-a5e8f2c04b39"`. |
| `scheduleNumber` | string | no | The depreciation schedule number. Unique within the tenant. Example: 'DS-0042'. Example: `"DS-0042"`. |
| `fixedAssetId` | number | yes | The internal number of the fixed asset the schedule depreciates. It is not the `id` that the fixed asset endpoints use. Example: `3187`. |
| `entityId` | number | yes | The internal number of the legal entity that owns the fixed asset. It is not the `id` that the legal entity endpoints use. Example: `1`. |
| `bookId` | number | yes | The internal number of the accounting book the fixed asset is tracked in. It is not the `id` that the accounting book endpoints use, or the `bookId` on a depreciation policy. Example: `1`. |
| `depreciationRuleId` | number | yes | The internal number of the depreciation rule applied to the fixed asset. A rule links a depreciation policy to a fixed asset type and sets the useful life. Example: `12`. |
| `status` | string | yes | The status of the schedule. Possible values: 'NotStarted' (no line has been recorded), 'Ongoing' (some lines have been recorded), 'Completed' (every line has been recorded), 'Disposed' (the fixed asset was disposed of), 'Voided' (the fixed asset was voided). Example: `"Ongoing"`. |
| `acquisitionDate` | date | yes | The date the fixed asset was acquired. Format: YYYY-MM-DD. It can be earlier than startDate. Example: `"2024-01-15"`. |
| `startDate` | date | yes | The date depreciation starts. Format: YYYY-MM-DD. Example: `"2024-02-01"`. |
| `endDate` | date | yes | The last day of depreciation. Format: YYYY-MM-DD. Example: `"2029-01-31"`. |
| `currency` | string | yes | The currency of the fixed asset. Format: ISO 4217, for example 'EUR'. Example: `"EUR"`. |
| `acquisitionValue` | decimal | yes | The acquisition cost of the fixed asset, in the `currency`. Example: `"24000.00"`. |
| `depreciableAmount` | decimal | yes | The total amount to depreciate over the schedule, in the `currency`. Formula: the fixed asset's depreciationStartValueAmount - salvageValueAmount, or when depreciationStartValueAmount is absent, acquisitionValue - salvageValueAmount. See depreciationStartValueAmount and salvageValueAmount on GET fixed-assets/:id. Example: `"21600.00"`. |
| `depreciatedAmount` | decimal | yes | The depreciation recorded on this schedule, in the `currency`. Formula: the sum of the recorded schedule lines. Lines that have not been recorded do not count, whatever their dates. Example: `"7560.00"`. |
| `remainingValue` | decimal | yes | The net book value of the fixed asset, in the `currency`. Formula: acquisitionValue - depreciatedAmount, or when the fixed asset has a depreciationStartValueAmount, depreciationStartValueAmount - depreciatedAmount. It is 0 once the fixed asset is voided, retired, or disposed of. Example: `"16440.00"`. |
| `lastModifiedDate` | date-time | yes | The date and time the depreciation schedule last changed, in UTC. Format: YYYY-MM-DDTHH:mm:ss.sssZ. Recording depreciation changes depreciatedAmount and remainingValue. It updates lastModifiedDate only when the schedule's status changes. Example: `"2026-08-14T09:12:33.000Z"`. |

```json
{
  "data": {
    "id": "7c2e5a91-3f84-4b60-9d17-a5e8f2c04b39",
    "scheduleNumber": "DS-0042",
    "fixedAssetId": 3187,
    "entityId": 1,
    "bookId": 1,
    "depreciationRuleId": 12,
    "status": "Ongoing",
    "acquisitionDate": "2024-01-15",
    "startDate": "2024-02-01",
    "endDate": "2029-01-31",
    "currency": "EUR",
    "acquisitionValue": "24000.00",
    "depreciableAmount": "21600.00",
    "depreciatedAmount": "7560.00",
    "remainingValue": "16440.00",
    "lastModifiedDate": "2026-08-14T09:12:33.000Z"
  },
  "diagnostics": [
    {
      "code": "<code>",
      "message": "<message>",
      "severity": "error",
      "path": [
        "<path>"
      ],
      "details": "<details>"
    }
  ]
}
```

## Errors

| Code | Status |
| --- | --- |
| `NOT_FOUND` | 400 |

## Statuses

- `400` — Invalid request or business failure. Codes: NOT_FOUND
- `401` — The request carries no valid access token.
- `403` — Not authorized
- `404` — Not found
- `429` — Too many requests from this client address. The response has no body and no `Retry-After` header.
- `500` — Internal server error