Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

You can either authorize with the organizationKey and the UserLoginName or you can use the apiToken (Image Added) for the authorization. For more informtaion information about the two different authorizations please have a look at the Postman Tutorial

Expand
titleAlternative: SOAP implementation (deprecated)

The authorization XML has to be encoded via HTML special characters (“<” in “&lt;” and “>” in “&gt;”). If this encoding is not done you will receive a HTTP 400 Bad Request error.
Higher programming languages takes automatically care of the conversation, so just in lower languages it is required (or also SOAPUI). You can find a configuration for the authorization for SOAP (XML) in the next lines:

Note: The next lines show a authorization with the organizationKey and the userLoginName.

Code Block
languagexml
themeEclipse
firstline0
<authorization>
	<organizationKey>4647688a-xxxx-xxxx-xxxx-xxxxxxxx</organizationKey>
	<userLoginName>your@email.address</userLoginName>
</authorization>

Inline-XML (with HTML special characters):

Code Block
languagexml
themeEclipse
firstline0
&lt;authorization&gt;
&lt;organizationKey&gt;4647688a-xxxx-xxxx-xxxx-xxxxxxxx&lt;/organizationKey&gt;
&lt;userLoginName&gt;your@email.address&lt;/userLoginName&gt;
&lt;/authorization&gt;

You can also authorize with the apiToken.  Please see the following configurations:

Code Block
languagexml
themeEclipse
firstline0
<authorization>
	<apiToken >hizit4enf8ellb6b5hwh5b------------------------------</apiToken >
</authorization>

Inline-XML (with HTML special characters):

Code Block
languagexml
themeEclipse
firstline0
&lt;authorization&gt;
	&lt;apiToken &gt;hizit4enf8ellb6b5hwh5b------------------------------&lt;/apiToken &gt; 
&lt;/authorization&gt;


...