# File formats The file-based endpoints — and the manual [work order import](../workflows/import-work-orders) and [item import](../workflows/manage-items) — accept **JSON** and **CSV** files. Files are transmitted as Base64-encoded content in a JSON body with `fileType` `0` (JSON) or `1` (CSV); uploads are never multipart. ## Work order files ### JSON A JSON **array of work order objects** in the shape of the [`WorkOrder` object](./work-orders.md#workorder-object). Per order, `number`, `dueDate`, and per request line `itemNumber` and `requestedAmount` are required; a file violating this fails the import. ```json title="work-orders.json" [ { "number": "WO-2026-0417", "description": "Assembly kit, line 3", "dueDate": "2026-07-15T12:00:00Z", "workOrderTypeName": "Picking", "designatedStorageName": "Main warehouse", "requests": [ { "itemNumber": "100-4711", "itemName": "Hex bolt M8", "requestedAmount": 12 }, { "itemNumber": "100-4712", "itemName": "Washer M8", "requestedAmount": 12 } ] } ] ``` ### CSV Comma-delimited, quoted fields supported, first line is a **header**. The header is name-driven: every header cell must exactly match one of the recognized column names — an unknown header aborts parsing. One CSV row is one **request line**; rows with the same `Number` are grouped into one work order. The first row of a group supplies the order-level fields, and its `DueDate` must be set. ```csv title="work-orders.csv — two orders, the first with two request lines" Number,ItemNumber,DueDate,RequestedAmount,ItemName,DesignatedStorageName WO-2026-0417,100-4711,2026-07-15,12,Hex bolt M8,Main warehouse WO-2026-0417,100-4712,2026-07-15,12,Washer M8,Main warehouse WO-2026-0418,100-4720,2026-07-16,3,Bracket left,Main warehouse ```

Column	Required
Number	yes
ItemNumber	yes
DueDate	yes
RequestedAmount	yes
Description, CustomerRequiredDeliveryDate, ItemName, ItemDescription, LanguageIsoCode, UnitOfMeasure, LotNumber, ExternalIdentifier, WorkOrderTypeName, DesignatedStorageName, DeliveryNumber, ExternalData, ItemExternalIdentifier, RequestExternalIdentifier, RequestExternalData, RequestType, Order, DesignatedLocationName, AlternativeStartNumber	no

### Request type In both formats, `RequestType` takes the number or the name of a request type, the name in any letter case: `0` / `Ignored`, `1` / `PickItem`, `2` / `PlaceItem`. `3` / `RelocateItem` is reserved for oneGRID Cloud's own Relocate Item process — a work order file that uses it fails the import, like any other invalid value. ## Item files ### JSON A JSON **array of item objects** in the shape of the [`Item` object](./items.md#item-object). An unparseable file returns `FileNotSupported`. ```json title="items.json" [ { "number": "100-4711", "name": "Hex bolt M8", "description": "Galvanized, 40 mm", "minimumStockQuantity": 100, "manufacturer": "Muster GmbH", "unitOfMeasure": 0 } ] ``` ### CSV Comma-delimited, quoted fields supported. Unlike work order CSVs, item CSVs are **positional**: the header row is skipped, and the columns must appear in exactly this order: ```csv title="items.csv — header text is ignored, column ORDER matters" Number,Name,Description,LanguageIsoCode,MinimumStockQuantity,Weight,Height,Width,Length,Volume,Manufacturer,UnitOfMeasure,ExternalIdentifier 100-4711,Hex bolt M8,"Galvanized, 40 mm",en,100,0.012,,,0.04,,Muster GmbH,0,ERP-ITEM-4711 ```

#	Column
1	Number
2	Name
3	Description
4	LanguageIsoCode
5	MinimumStockQuantity
6	Weight
7	Height
8	Width
9	Length
10	Volume
11	Manufacturer
12	UnitOfMeasure
13	ExternalIdentifier (may be omitted)

Any row that fails validation aborts the whole file.