| POST | /stock/{brand}/acceptDelivery | Manual Order Reception |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| brand | path | string | Yes | Brand |
| posCode | body | string | Yes | Pos Legacy Code with Legacy System ID, e.g. ES123:123456 |
| deliveryNotes | body | List<AcceptDeliveryNoteItem> | Yes | Received deliveries |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| deliveryNotesNumber | form | long | Yes | Delivery Notes Number, e.g. 7040123456 |
| deliveryNotesDate | form | DateTime | Yes | Delivery Notes Date, e.g. 2022-10-10 |
| deliveryNotesLineNumber | form | int | Yes | Delivery Notes Line Number (DeliveryNotesNoSplit), e.g. 10 |
| receivedQuantity | form | int | Yes | ReceivedQuantity, e.g. 2 |
| serialNumbers | form | List<string> | No | Serial Numbers, e.g. '6361234', '6361235' |
To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json
To embed the response in a jsonp callback, append ?callback=myCallback
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
POST /stock/{brand}/acceptDelivery HTTP/1.1
Host: dev-api-booster.richemont.com
Accept: application/json
Content-Type: application/json
Content-Length: length
{"brand":"String","posCode":"String","deliveryNotes":[{"deliveryNotesNumber":0,"deliveryNotesDate":"\/Date(-62135596800000-0000)\/","deliveryNotesLineNumber":0,"receivedQuantity":0,"serialNumbers":["String"]}]}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{}