Booster.Microservices

VerifyAuthorizationRequest

The following routes are available for this service:
GET	/warranty/v1/security/{mnemonicId}
GET	/warranty/v1/security/{mnemonicId}/site/{posId}
GET	/warranty/v1/security/{mnemonicId}/brand/{brandTrigram}
GET	/warranty/v1/security/{mnemonicId}/site/{posId}/brand/{brandTrigram}

**VerifyAuthorizationRequest** Parameters:
Name	Parameter	Data Type	Required
mnemonicId	path	string	No
posId	path	int?	No
brandTrigram	path	string	No

**BaseRequest<TResponse>** Parameters:
Name	Parameter	Data Type	Required
sid	form	string	No
app	form	string	No
_os	form	string	No
_appVersion	form	string	No
_searchMethod	form	string	No

**VerifyAuthorizationResponse** Parameters:
Name	Parameter	Data Type	Required	Description
isAllowed	form	bool	No

**BaseResponse** Parameters:
Name	Parameter	Data Type	Required
_xmlns	form	string	No
_type	form	string	No
_source	form	string	No
_tstamp	form	string	No
_user	form	string	No
_env	form	string	No
_uri	form	string	No
_query	form	string	No

**VerifyAuthorizationResponse** Parameters:
Name	Parameter	Data Type	Required	Description
isAllowed	form	bool	No

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.

GET /warranty/v1/security/{mnemonicId} HTTP/1.1 
Host: qp-microservices-booster.richemont.com 
Accept: application/json

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

{"isAllowed":false,"_xmlns":"String","_type":"String","_source":"String","_tstamp":"String","_user":"String","_env":"String","_uri":"String","_query":"String"}