<back to all web services
SetPositions
The following routes are available for this service:| All Verbs | /SetPositions | | |
|---|
SetPositions Parameters:| Name | Parameter | Data Type | Required | Description |
|---|
| Positions | query | Position[] | Yes | Key identifying a location |
| StockroomName | query | string | No | Optional: name of the stockroom where the position is located |
| Overwrite | query | bool? | No | Optional: overwrite existing positions defined with the same key: Yes by default |
Position Parameters:| Name | Parameter | Data Type | Required | Description |
|---|
| ID | form | int | No | |
| Key | form | string | No | |
| Pixel | form | int | No | |
| Width | form | int | No | |
| AreaID | form | int | No | |
| AreaLabel | form | string | No | |
| Label | form | string | No | |
| StockroomID | form | long? | No | |
To override the Content-type in your clients, use the HTTP Accept Header, append the .xml suffix or ?format=xml
HTTP + XML
The following are sample HTTP requests and responses.
The placeholders shown need to be replaced with actual values.
POST /SetPositions HTTP/1.1
Host: webadmin.clouddemo2.pickeos.com
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<SetPositions xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/GoToLightAPI">
<Overwrite>false</Overwrite>
<Positions>
<Position>
<AreaID>0</AreaID>
<AreaLabel>String</AreaLabel>
<ID>0</ID>
<Key>String</Key>
<Label>String</Label>
<Pixel>0</Pixel>
<StockroomID>0</StockroomID>
<Width>0</Width>
</Position>
</Positions>
<StockroomName>String</StockroomName>
</SetPositions>