# Retrieve a landed cost item

Operation ID: `getLandedCostItem`

Group: Inventory › Landed Cost Items

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

`GET /inventory/landed-cost-items/{id}`

Read-only: Reads and returns; changes nothing.

Retrieves a landed cost item, with the names of its item, account, and costing element type.

## 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 landed cost item you want to retrieve. Format: UUID. |

## Response

`200` Success

Under `data` (getLandedCostItemOutput):

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `id` | string | yes | The unique identifier for the landed cost item. Format: UUID. Example: `"9f3c71a4-2e58-4b06-8d19-5a7e0c34b2f1"`. |
| `itemId` | string | no | The unique identifier of the item this landed cost item covers, such as a freight, handling, or insurance service item. Format: UUID. A vendor bill line for this item counts as a landed cost charge. Absent when the landed cost item covers only an account. See `id` on GET inventory/items/:id (getItem). Example: `"3d81e07c-95a2-4f63-b1c8-27e5a94d0b36"`. |
| `itemCode` | string | no | The code of the item in `itemId`. Example: `"SVC-FREIGHT"`. |
| `itemName` | string | no | The name of the item in `itemId`. Example: `"Inbound freight"`. |
| `accountId` | string | no | The unique identifier of the general ledger account this landed cost item covers. Format: UUID. A vendor bill line with this expense account counts as a landed cost charge. Absent when the landed cost item covers only an item. See `id` on GET accounting/accounts/:id (getAccount). |
| `accountNumber` | string | no | The number of the account in `accountId`. |
| `accountName` | string | no | The name of the account in `accountId`. |
| `allocationMode` | string | no | How a charge is spread (allocated) over the receipt lines. Possible values: 'Equal', 'Quantity', 'LineTotal', 'Weight', 'Volume'. Example: `"Weight"`. |
| `costingElementTypeId` | string | no | The unique identifier of the costing element type for this landed cost item's charges. Format: UUID. A costing element type is a category of inventory cost, such as duties. When a landed cost is committed, its inventory revaluations for these charges get this costing element type. Absent when the landed cost item has none. Example: `"c4a90e21-7b35-4d18-9e02-6f13a85c7d40"`. |
| `costingElementTypeCode` | string | no | The code of the costing element type in `costingElementTypeId`. Example: `"FRT"`. |
| `costingElementTypeName` | string | no | The name of the costing element type in `costingElementTypeId`. Example: `"Freight"`. |
| `active` | boolean | no | Whether the landed cost item is active. Example: `true`. |
| `createdDate` | date-time | no | The date and time the landed cost item was created, in UTC. Format: YYYY-MM-DDTHH:mm:ss.sssZ. |
| `lastModifiedDate` | date-time | no | The date and time the landed cost item last changed, in UTC. Format: YYYY-MM-DDTHH:mm:ss.sssZ. Example: `"2026-08-18T09:14:22.517Z"`. |

```json
{
  "data": {
    "id": "9f3c71a4-2e58-4b06-8d19-5a7e0c34b2f1",
    "itemId": "3d81e07c-95a2-4f63-b1c8-27e5a94d0b36",
    "itemCode": "SVC-FREIGHT",
    "itemName": "Inbound freight",
    "accountId": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
    "accountNumber": "<accountNumber>",
    "accountName": "<accountName>",
    "allocationMode": "Weight",
    "costingElementTypeId": "c4a90e21-7b35-4d18-9e02-6f13a85c7d40",
    "costingElementTypeCode": "FRT",
    "costingElementTypeName": "Freight",
    "active": true,
    "createdDate": "2026-01-15T09:30:00.000Z",
    "lastModifiedDate": "2026-08-18T09:14:22.517Z"
  },
  "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