Richemont.Booster2.PublicApi

GrantElevateConsent

The following routes are available for this service:
POST	/customer/{brand}/{elevateCustomerId}/grantElevateConsent	Update Elevate customer consent to 'Approved'	Currently the API sets Elevate customer consent only to 'Approved' status

**GrantElevateConsent** Parameters:
Name	Parameter	Data Type	Required	Description
elevateCustomerId	path	string	No	Elevate customer ID
posCode	body	string	Yes	POS Legacy
brand	path	string	Yes	Brand e.g. CAR, MTB
phone	body	string	No	Phone e.g. cn: 13888889999, jp: 352858088, kr: 023123456. Email or full phone required
phoneCountryPrefix	body	string	No	Prefix Country Id e.g. it, fr, az. Email or full phone required
email	body	string	No	Customer email. Email or full phone required

**GrantElevateConsentResponse** Parameters:
Name	Parameter	Data Type	Required	Description
salesforceStandardId	form	string	Yes	Salesforce Standard ID

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

To embed the response in a jsonp callback, append ?callback=myCallback

HTTP + JSON

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

POST /customer/{brand}/{elevateCustomerId}/grantElevateConsent HTTP/1.1 
Host: dev-api-booster.richemont.com 
Accept: application/json
Content-Type: application/json
Content-Length: length

{"elevateCustomerId":"String","posCode":"String","brand":"String","phone":"String","phoneCountryPrefix":"String","email":"String"}

HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length

{"salesforceStandardId":"String"}