| 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 item created in Booster |
| saleRepresentativeEmails | query | List<string> | No | Emails of Sale Representatives |
| promoterTypeId | query | string | No | Promoter Type ID |
To override the Content-type in your clients, use the HTTP Accept Header, append the .xml suffix or ?format=xml
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: application/xml
Content-Type: application/xml
Content-Length: length
<PatchSellout xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/Richemont.Booster2.PublicApi.Sellout.ServiceModel">
<promoterTypeId>String</promoterTypeId>
<saleId>0</saleId>
<saleRepresentativeEmails xmlns:d2p1="http://schemas.microsoft.com/2003/10/Serialization/Arrays">
<d2p1:string>String</d2p1:string>
</saleRepresentativeEmails>
</PatchSellout>
HTTP/1.1 200 OK Content-Type: application/xml Content-Length: length <PatchSelloutResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/Richemont.Booster2.PublicApi.Sellout.ServiceModel" />