---
agentTools:
  projectIndex: https://apidocs.shipmonk.com/llms.txt
---

# v1.027

**Receivings can carry ShipMonk-agreed attributes.**
Create Receiving accepts a new optional `attributes` list, and Get Receiving / Receivings List return it. Only keys and values agreed with ShipMonk for your account are accepted; contact <api@shipmonk.com> before sending them.

***

## 🚀 New Endpoints

*None*

## 🛠 Schema & Property Updates

* **Create Receiving** (`POST /v1/integrations/receiving`) — new optional `attributes` list of `name` / `value` pairs. A submitted list replaces the stored one in full, so an attribute missing from it is unset; omitting the property (or passing `null`) leaves the stored attributes untouched.
* **Get Receiving** (`GET /v1/integrations/receiving`) and **Receivings List** (`GET /v1/integrations/receivings-list`) — new `attributes` list, returning each attribute value as the text it was submitted with.

## 📦 New Support Schemas

* **`ReceivingAttributeInput`** — the `name` / `value` pair accepted on create and update.
* **`PublicApiReceivingAttributeOutput`** — the `name` / `value` pair returned on the receiving.

## 📖 Documentation & Constraints Changes

* **Create Receiving** (`POST /v1/integrations/receiving`) — `value` is always text, and each key defines the values it accepts. An unrecognized `name`, a `name` sent twice in one list, a `value` not accepted for that attribute, or a key not enabled for your account is rejected with a 400.
* **Create Receiving** (`POST /v1/integrations/receiving`) — the stored `attributes` are frozen once the warehouse starts processing the receiving, like the other receiving-level fields. Omitting the property, or sending a list identical to the stored one, is still accepted.

*No endpoints, fields, or required-status were removed or changed — fully backward-compatible.*