---
title: "Changes to Create a new item cut from an activated material shape. The shape determines the item's material\nthickness, material form and length unit, so those are not sent on the request — select the shape that\ncarries the combination you want. The item is always created as a Buy item measured in Pieces, its\nnumber is generated from the shape and the dimensions supplied (e.g. `Steel A36 Sheet 1/4\": 48\"x120\"`),\nand its weight is calculated from the shape's density.\n            \nThe shape must already be activated for the shop. An id that exists only in the materials database is\nrejected with a 404 — activate it first with the Material Activate endpoint. This endpoint never\nactivates a shape, because activating one also un-archives every existing non-remnant item that uses it.\n            \nA material item's number is derived rather than caller-supplied, so the same shape and dimensions always\nresolve to the same item. If that item already exists it is returned as-is instead of a duplicate being\ncreated, and if it was archived it is un-archived — meaning a successful response may carry the id of an\nitem that predates the request. Check whether an item with the expected number already exists if the\ndistinction matters to your integration. The number does not encode remnant state, so\n`isRemnant` is honoured only when a new item is created and is ignored on that collision."
method: POST
path: "/api/items/material"
---

# Changes to Create a new item cut from an activated material shape. The shape determines the item's material
thickness, material form and length unit, so those are not sent on the request — select the shape that
carries the combination you want. The item is always created as a Buy item measured in Pieces, its
number is generated from the shape and the dimensions supplied (e.g. `Steel A36 Sheet 1/4": 48"x120"`),
and its weight is calculated from the shape's density.
            
The shape must already be activated for the shop. An id that exists only in the materials database is
rejected with a 404 — activate it first with the Material Activate endpoint. This endpoint never
activates a shape, because activating one also un-archives every existing non-remnant item that uses it.
            
A material item's number is derived rather than caller-supplied, so the same shape and dimensions always
resolve to the same item. If that item already exists it is returned as-is instead of a duplicate being
created, and if it was archived it is un-archived — meaning a successful response may carry the id of an
item that predates the request. Check whether an item with the expected number already exists if the
distinction matters to your integration. The number does not encode remnant state, so
`isRemnant` is honoured only when a new item is created and is ignored on that collision.

`POST /api/items/material`

> Every recorded change to this endpoint, newest first.

## Timeline

Changed in 1 of 23 revisions.

- **2026-09-11** `c00251431237` — 1 info

## Changes

- **2026-09-11** `c00251431237` — 1 info
  - endpoint added

---

[Operation](https://skmtc.dev/fulcrumpro/apis/fulcrum-publicapi/docs/api/items/material/post.md) · [API](https://skmtc.dev/fulcrumpro/apis/fulcrum-publicapi.md) · [Page](https://skmtc.dev/fulcrumpro/apis/fulcrum-publicapi/changes/api/items/material/post)