| PATCH | /warranty/{saleId} | Patch Sellout | Patch Sellout with Updated info |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| saleId | path | int | Yes | Unique Identifier of the Sell-out created in Booster |
| saleRepresentativeEmails | query | List<string> | No | Emails of Sale Representatives |
| promoterTypeId | query | string | No | Promoter Type ID |
| saleItems | query | List<SaleItem> | No | Items list of the sale |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| saleDetailId | form | int | Yes | Unique Identifier of the Sell-out item created in Booster |
| unitPrice | form | decimal? | No | Sold Price to the end-client |
| currencyCode | form | string | No | Currency of the sold price to the end-client |
To override the Content-type in your clients, use the HTTP Accept Header, append the .other suffix or ?format=other
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
PATCH /warranty/{saleId} HTTP/1.1
Host: dev-api-booster.richemont.com
Accept: text/jsonl
Content-Type: text/jsonl
Content-Length: length
{"saleId":0,"saleRepresentativeEmails":["String"],"promoterTypeId":"String","saleItems":[{"saleDetailId":0,"unitPrice":0,"currencyCode":"String"}]}
HTTP/1.1 200 OK
Content-Type: text/jsonl
Content-Length: length
{}