Richemont.Booster2.PublicApi

<back to all web services

GetSaleDetails

Requires Authentication
The following routes are available for this service:
GET/warrantyGet a list of Sale DetailsGet a list of Sale Details based on the search parameters submitted
GetSaleDetails Parameters:
NameParameterData TypeRequiredDescription
brandquerystringYesRichemont Brand ID
posCodequerystringYesRichemont POS code
documentNumberquerystringNoReceipt or Invoice Number
documentDateFromqueryDateTime?NoDate of the Sell-out Start
documentDateToqueryDateTime?NoDate of the Sell-out End
articleCodequerystringNoRichemont Reference Code of the item
serialNumberquerystringNoSerial Number of the item
saleDetailIdqueryint?NoUnique Identifier of the Sell-out created in Booster
saleIdqueryint?NoUnique Identifier of the Sell-out created in Booster
boosterCustomerIdqueryint?NoBooster Customer Id
warrantyExtensionStatusIdsqueryList<int>NoPossible warranty extention status IDs, 1 (Activated), 2 (Requested), 3 (Refused), 4 (Error), 5 (Action Required), 6 (Pending)
productCategoriesqueryList<ProductCategory>NoProduct Categories
pagequeryintYesIndex of the result set returned
itemsqueryintYesSize of the result set returned
noCountqueryboolNoOmit precise record count - save on performance
sortByquerystringNoSort Expression, Possible values: 'SaleDetailIdDESC', 'DocumentDate'.
ProductCategory Parameters:
NameParameterData TypeRequiredDescription
brandCategoryIdformstringNoBrand Category ID
grandCategoryIdformstringYesGrand Category ID
masterCategoryIdformstringNoMaster Category ID
categoryIdformstringNoCategory ID
subCategoryIdformstringNoSub Category ID
GetSaleDetailsResponse Parameters:
NameParameterData TypeRequiredDescription
pageformintYesIndex of the result set returnedr
itemsformintYesSize of the result set returned
totalPagesformintYesTotal amount of pages / result sets
totalResultsformintYesTotal amount of results
elementsformIEnumerable<SaleDetail>YesList of Sale Details
SaleDetail Parameters:
NameParameterData TypeRequiredDescription
saleIdformintYesUnique Identifier of the Sell-out created in Booster
saleDetailIdformintYesUnique Identifier of the Sell-out created in Booster
boosterCustomerIdformint?NoBooster Customer Id
posCodeformstringYesRichemont POS code
documentNumberformstringNoReceipt or Invoice Number
documentDateformstringYesDate of the Sell-out
documentLineNumberformint?NoPosition Number
articleCodeformstringYesRichemont Reference Code of the item
serialNumberformstringNoSerial Number of the item
quantityformint?YesUse positive for standard Sell-out and negative quantity for return
retailPriceformdecimal?NoRetail Price
unitPriceformdecimal?NoSold Price
currencyCodeformstringNoCurrency of the sold price
ccpStatusCodeformstringNoCCP Status Code
ccpStatusDescriptionformstringNoCCP Status Description
retriggerEnabledformboolNoCCP Retrigger enable
warrantyExtentionStatusIdformint?NoWarranty Extention Status
warrantyExtentionStatusDescriptionformstringNoWarranty Extention Status
saleRepresentativeEmailsformList<string>NoSale Representative Email
promoterTypeIdformstringNoPromoter Type IDs, possible values are: DAI, FIT, GRT
typeformstringYesSellout Type, possible values are: 'standard' or 'consigned'
originalSaleDetailIdformint?NoOriginal Sale Detail Id

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

HTTP + XML

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

GET /warranty HTTP/1.1 
Host: dev-api-booster.richemont.com 
Accept: application/xml
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length

<GetSaleDetailsResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/Richemont.Booster2.PublicApi.Sellout.ServiceModel">
  <elements i:nil="true" />
  <items>0</items>
  <page>0</page>
  <totalPages>0</totalPages>
  <totalResults>0</totalResults>
</GetSaleDetailsResponse>