Create a landed cost item

Operation ID: createLandedCostItem

Group: Inventory › Landed Cost Items

Open in the interactive reference

POST /inventory/landed-cost-items

Retry-safe: A write that accepts Idempotency-Key: repeating a request with the same key replays the stored answer instead of executing twice.

Creates a landed cost item. Send itemId, accountId, or both. With both, a vendor bill line matches when either its item or its expense account matches. Each itemId and each accountId can be used by only one landed cost item, including one whose active is false, so creating a second one for the same item or account fails. To change an existing landed cost item, use PATCH inventory/landed-cost-items/:id. The response contains only the id. To see the created landed cost item, use GET inventory/landed-cost-items/:id.

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.
Idempotency-Key header string no An opaque caller-chosen string (1-255 characters) that makes this request safe to retry. Repeating the same key with an identical request body replays the original response instead of re-executing - but only once that original request succeeded; a failed attempt re-executes on retry. Repeating the key with a different body is answered with 422. A key still in flight is answered with 409 - as is a key whose original request was interrupted before it finished, for a few minutes afterwards, until that attempt is presumed dead. A completed response stays replayable for 24 hours. The key is scoped to the caller, not to the action: reusing it for a different action is answered with 409 or 422 rather than treated independently. On read actions this header is ignored. On write actions that cannot offer the guarantee it is answered with 400 IDEMPOTENCY_NOT_SUPPORTED rather than silently ignored.

Request body

Required, application/json: createLandedCostItemInput.

Field Type Required Description
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. See id on GET inventory/items/:id (getItem). Example: "3d81e07c-95a2-4f63-b1c8-27e5a94d0b36".
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. See id on GET accounting/accounts/:id (getAccount).
allocationMode string yes How a charge is spread (allocated) over the receipt lines. Accepted 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. Example: "c4a90e21-7b35-4d18-9e02-6f13a85c7d40".
active boolean no Whether the landed cost item is active. Defaults to true. 
{
  "itemId": "3d81e07c-95a2-4f63-b1c8-27e5a94d0b36",
  "accountId": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
  "allocationMode": "Weight",
  "costingElementTypeId": "c4a90e21-7b35-4d18-9e02-6f13a85c7d40",
  "active": true
}

Response

200 Success

Under data (createLandedCostItemOutput):

Field Type Required Description
id string yes The unique identifier for the created landed cost item. Format: UUID. Example: "9f3c71a4-2e58-4b06-8d19-5a7e0c34b2f1". 
{
  "data": {
    "id": "9f3c71a4-2e58-4b06-8d19-5a7e0c34b2f1"
  },
  "diagnostics": [
    {
      "code": "<code>",
      "message": "<message>",
      "severity": "error",
      "path": [
        "<path>"
      ],
      "details": "<details>"
    }
  ]
}

Response headers

Errors

Code Status
NO_SELECTOR 400
REFERENCE_NOT_FOUND 400
UNKNOWN_ALLOCATION_MODE 400
DUPLICATE 400
IDEMPOTENCY_KEY_CONFLICT 409
IDEMPOTENCY_PAYLOAD_MISMATCH 422

Statuses