Digital Signature API: Authentication

For the REST-like calls, an authentication with a valid SELL&SIGN account is required.
The authentication can be done in 2 differents ways:

  • using a URL parameter token
  • using a HTTP header token

Obviously it’s also possible to operate within an authenticated HTTP session.

Activate your License

To get your authentification token, you need a valid SELL&SIGN online licence.

Authentication using URL parameters

To use this method of authentication, you have to add the j_token setting to your request like following :

https://<host>/calinda/hub/selling/model/<class>/<action type>?action=<method>&<parameters>&j_token=<URL encoded token>

Caution: to pass some characters into an URL, they have to be URL-encoded.
For example the string
If needed, you will find here an online service which lets you URL-encode a string of characters.


Authentication using HTTP header

To use this authentication way, a manipulation of the HTTP header is necessary in order to add the j_token header.

In JavaScript, it is possible to modify the header with the Ajax object of jquery. On the configuration settings of the ajax call ($ajax), you can add the attribute « beforeSend » and give to it a function named setHeader. It will receive an « xhr » object in settings on which you will affect the header value by using the function « setRequestHeader ».


    	  beforeSend: setHeader,
      function setHeader(xhr) {
          xhr.setRequestHeader('j_token', 'abcde|RH/YgwxB4LA3jJ1gi9m6JF7iFnK/JKbT');

In Java, by using the Apache HTTP Client library, you can call the method « setHeader » on instances of « HttpPost » or « HttpGet ».


HttpPost post = new HttpPost(resolveURL(method));
post.setHeader("j_token", my_token);
Digital Signature API: Authentication
Rate this post