;
Loading

Loading

Signder - REST API Web Signature service

Create your temporary account

Create your temporary account

Subscribe

Download a Web MVC with instructions to help setup your form.

Signder offers you a full version of the source code to connect to its signature REST API.

Download a web MVC example.

Download a zip file

The previously entered user ID and password for your account must be inserted in the "Web.config" file. The "Web.config" file is present in "Signder_csharp" projects. Using your own authentication parameters is essential for the connection to the REST server.

Read and follow instructions to help setup your form.

In the project "Samples.Report" project folder contains two samples RDLC forms, one in French and one in English.

The Properties window (f4) is an important tool to help you customize your form.

In the example form, the fields "Expr" are used to insert dynamic data. A right click on these fields and selecting the option "expression" allows you to view or modify the dynamic value of the field.

Download a JavaScript Visual Studio solution.

Signder offers you a full version of the source code to connect to its signature REST API.

Download a JavaScript example.

Download a zip file

The previously entered user ID and password for your account must be inserted in the "Index.js" file. The "Index.js" file is present in" Signder_Javascript" projects. Using your own authentication parameters is essential for the connection to the REST server.

Understanding the architecture of our REST server.

Architecture of our REST server.

Request
Route
Description
POST
signder.net/api/signatures/{uniqueKey}
Creates a new signature. Returns the created signature model.
POST
signder.net/api/signatures/{uniqueKey}/signer/{qty}
Receives in parameter an array with optional customized values for the full name and title, the reference code and the signature security code.
[{ "fullname":"Full Name", "securitycode":"The security code.", "reference":"Reference code" }]
GET
signder.net/api/requests
Returns signature requests
GET
signder.net/api/requests/{uniqueKey}
Returns associated signature requests to {uniqueKey}.
GET
signder.net/api/signatures
Returns the content of current signatures to all signers.
GET
signder.net/api/signatures/{uniqueKey}
Returns the current signature(s) associeted with the {uniqueKey}.
GET
signder.net/api/signatures/{uniqueKey}/history
Returns the signatures, current or otherwise, associated with the {uniqueKey}.
PUT
signder.net/api/requests/{uniqueKey}/status/{statuscode}
Replaces the status of the signature or signatures. This responds with an http code of confirmation or failure. Used for the opening and closing of a request.

Customized javascript examples with and without the "signature" object.

A request for signature without the JSON object, "signature".

           
$.ajax({
    type: 'Post',
    url: "https://signder.net/api/Signatures/"+uniqueKey,
    beforeSend: function (xhr) {
        xhr.setRequestHeader('Authorization', 'Basic ' + btoa('[Your user name]:[Your password]'));
    },
    error: function (xhr, textStatus, errorThrown) {
        alert("Error");
    },
    success: function (data) {
        alert("Success");
    }
});

JSON object "Request" description

Property
Description
accountName
Account associated with the signature request
uniqueKey
Single code associated with the signature request
createdOn
Date of signature request
lastModificationOn
Latest modification done on the signature request
status
Signature request status


Description of the JSON object, "signature".

Property
Description
fullname
Full Name
signOn
Date of the last signature.
ip
Signer's ipv4 address
base64HandWriting
Data from the image of the signature.
token
Number associated with the signature
createdOn
Date of signature request
reference
Number for the position of the signature on the document.
secureCode
The security code requested for the signature.

A request for signature with the JSON object, "signature".

In the following example, the object built in the "data" field of the http request allows the customization of the signature request. In this example, an additional level of security has been integrated, the signer's full name and a security code have been added to the signature request. The Signder API will interpret this request by asking the signer for the security code related to his or her signature. The signature cannot be completed without the security code.

$.ajax({
    type: 'Post',
    url: "https://signder.net/api/Signatures/"+uniqueKey + "/signer/1",
                data: ' [ {"fullname": "'[Full Name]'", "secureCode":"'[The security code.]'" } ] ',
    beforeSend: function (xhr) {
        xhr.setRequestHeader('Authorization', 'Basic ' + btoa('Your user name:Your password'));
    },
    error: function (xhr, textStatus, errorThrown) {
        alert("Error");
    }
    success: function (data) {
        alert("Success");
    }
});
    
Subscribe

Contact Us

1430 rue Belanger,
Montreal, Quebec
H2G 1A4, Canada

1.855.514.2727