Richemont.Booster2.PublicApi

<back to all web services

DeleteUserAuth

Requires Authentication
The following routes are available for this service:
DELETE/user/{brand}/{posCode}/{userId}/authorizeDelete the authorization for the given external user and for the given POS
DeleteUserAuth Parameters:
NameParameterData TypeRequiredDescription
userIdpathstringYesUser's UserID (GUID). E.g. '731cd7f3-a781-48bf-b43d-310273895ce2'
brandpathstringYesBrand Trigram, e.g. CAR, IWC, VAC
posCodepathstringNoPos code

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.

DELETE /user/{brand}/{posCode}/{userId}/authorize HTTP/1.1 
Host: dev-api-booster.richemont.com 
Accept: application/xml
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length

<DeleteUserAuthResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/Richemont.Booster2.PublicApi.Security.ServiceModel" />