| GET | /stock/{brand}/transferRequest | Get Transfer Requests | Get a list of Transfer Requests related to given POSes |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| brand | path | string | Yes | Brand Trigram, e.g. CAR, IWC |
| posCodes | query | List<string> | Yes | List of POS Codes in interest, e.g. ES100:102048,ES100:101469 |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| transferRequestId | form | int | Yes | Transfer Request ID, e.g. 1234567 |
| status | form | string | Yes | Transfer Request Status: 'PEN', 'ACC', 'ERR', 'INP', 'COM', 'REJ', 'CAN' |
| createdDate | form | string | Yes | Transfer Request creation date e.g. 2022-01-01 |
| createdBy | form | string | Yes | Transfer Request created user |
| posCodeFrom | form | string | Yes | POS Code of the transfer Source POS, e.g. ES100:102048 |
| posCodeTo | form | string | Yes | POS Code of the transfer Target POS, e.g. ES100:101469 |
| articleCode | form | string | Yes | Legacy Article Code of the item to be transferred |
| serialNumber | form | string | No | Serial Number of the Article to be transferred |
| notes | form | string | No | Notes |
| returnNumber | form | long? | No | Return Number of the Authroization form document / PDF if exists |
| context | form | string | No | Context of the Transfer request, can be either PUSH or PULL |
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.
GET /stock/{brand}/transferRequest HTTP/1.1
Host: dev-api-booster.richemont.com
Accept: application/json
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length []