INTERNAL-Authorization

AuthorizeToken

The following routes are available for this service:
GET,POST	/authorizetoken/{Service}/{TokenString}

**AuthorizeToken** Parameters:
Name	Parameter	Data Type	Required	Description
TokenString	path	string	Yes
Service	path	string	Yes

**AuthorizeBaseResponse** Parameters:
Name	Parameter	Data Type	Required
IsAuthorized	form	bool	No
Settings	form	List<Setting>	No
SuggestedStatusCode	form	int	No
SuggestedResponseMessage	form	string	No
Reason	form	string	No
CustomerId	form	Guid?	No

**Setting** Parameters:
Name	Parameter	Data Type	Required
Name	form	string	No
StringValue	form	string	No
BooleanValue	form	bool	No
DataType	form	string	No

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.

POST /authorizetoken/{Service}/{TokenString} HTTP/1.1 
Host: nkapi-sgepz3-auth.azurewebsites.net 
Accept: application/xml
Content-Type: application/xml
Content-Length: length

<AuthorizeToken xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/Norkart.Api.Authorization.ServiceModel">
  <Service>String</Service>
  <TokenString>String</TokenString>
</AuthorizeToken>

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

<AuthorizeTokenResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/Norkart.Api.Authorization.ServiceModel">
  <CustomerId i:nil="true" />
  <IsAuthorized>false</IsAuthorized>
  <Reason>String</Reason>
  <Settings>
    <Setting>
      <BooleanValue>false</BooleanValue>
      <DataType>String</DataType>
      <Name>String</Name>
      <StringValue>String</StringValue>
    </Setting>
  </Settings>
  <SuggestedResponseMessage>String</SuggestedResponseMessage>
  <SuggestedStatusCode>0</SuggestedStatusCode>
</AuthorizeTokenResponse>