| POST | /stock/{brand}/movement/export | Export Stock Movement Data |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| downloadRequestId | body | string | Yes | Export Request ID of the API Consumers |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| brand | form | string | Yes | Brand |
| posCodes | form | List<string> | Yes | POS Legacy |
| movementTypeIds | form | List<int> | No | Movement Type Ids |
| searchKey | form | string | No | Search Key (Article or SerialNumber) |
| dateFrom | form | DateTime? | No | In Stock Since date from |
| dateTo | form | DateTime? | No | In Stock Since date to |
| sortBy | form | string | No | Sort by date could be: 'DateDESC' or 'DateASC' (default is descending) |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| asyncTaskId | form | Guid | Yes | Unique Identifier of the Export Request created |
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}/movement/export HTTP/1.1
Host: dev-api-booster.richemont.com
Accept: application/json
Content-Type: application/json
Content-Length: length
{"downloadRequestId":"String","brand":"String","posCodes":["String"],"movementTypeIds":[0],"searchKey":"String","dateFrom":"\/Date(-62135596800000-0000)\/","dateTo":"\/Date(-62135596800000-0000)\/","sortBy":"String"}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"asyncTaskId":"00000000000000000000000000000000"}