Richemont.Booster2.PublicApi

ExtendSellOut

The following routes are available for this service:
POST	/warranty/{saleDetailId}/extend	Extend a Sell-Out	Delete a sell-out you are authorized for

**ExtendSellOut** Parameters:
Name	Parameter	Data Type	Required	Description
saleDetailId	path	int	Yes	Unique Identifier of the Sell-out created in Booster

**ExtendSellOutResponse** Parameters:
Name	Parameter	Data Type	Required	Description
ccpStatus	form	StatusWarrantyExtension	Yes	ccp substatus information
boosterStatus	form	Status	Yes	ccp main status information

**StatusWarrantyExtension** Parameters:
Name	Parameter	Data Type	Required	Description
retriggerEnabled	form	bool	Yes	Information about if a warranty can be retriggered

**Status** Parameters:
Name	Parameter	Data Type	Required	Description
id	form	string	Yes	Unique Identifier of the Sell-out created in Booster
description	form	string	Yes	Unique Identifier of the Sell-out created in Booster

To override the Content-type in your clients, use the HTTP Accept Header, append the .jsv suffix or ?format=jsv

HTTP + JSV

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

POST /warranty/{saleDetailId}/extend HTTP/1.1 
Host: dev-api-booster.richemont.com 
Accept: text/jsv
Content-Type: text/jsv
Content-Length: length

{
	saleDetailId: 0
}

HTTP/1.1 200 OK
Content-Type: text/jsv
Content-Length: length

{
	ccpStatus: 
	{
		retriggerEnabled: False,
		id: String,
		description: String
	},
	boosterStatus: 
	{
		id: String,
		description: String
	}
}