ImzagerServices

SignDocument

The following routes are available for this service:
All Verbs	/SignDocument/{ClientKey}

"use strict";
export class SignDocumentResponse {
    /** @param {{Result?:boolean,ServiceSuccessResult?:boolean,ErrorMesage?:string}} [init] */
    constructor(init) { Object.assign(this, init) }
    /** @type {boolean} */
    Result;
    /** @type {boolean} */
    ServiceSuccessResult;
    /** @type {string} */
    ErrorMesage;
}
export class SignDocument {
    /** @param {{ClientKey?:string,AuthorizationID?:string,UserSSN?:string,DocumentId?:number,SignerSSN?:string,SignerEMail?:string,SignMessage?:string}} [init] */
    constructor(init) { Object.assign(this, init) }
    /** @type {string} */
    ClientKey;
    /** @type {string} */
    AuthorizationID;
    /** @type {string} */
    UserSSN;
    /** @type {number} */
    DocumentId;
    /** @type {string} */
    SignerSSN;
    /** @type {string} */
    SignerEMail;
    /** @type {string} */
    SignMessage;
}

JavaScript SignDocument DTOs

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.

POST /SignDocument/{ClientKey} HTTP/1.1 
Host: imzagerservices.eyyubiye.bel.tr 
Accept: application/json
Content-Type: application/json
Content-Length: length

{"ClientKey":"String","AuthorizationID":"String","UserSSN":"String","DocumentId":0,"SignerSSN":"String","SignerEMail":"String","SignMessage":"String"}

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

{"Result":false,"ServiceSuccessResult":false,"ErrorMesage":"String"}