ImzagerServices

SignDocumentPDF

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

"use strict";
export class SignDocumentPDFResponse {
    /** @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 SignDocumentPDF {
    /** @param {{ClientKey?:string,AuthorizationID?:string,UserSSN?:string,DocumentId?:number,Message?:string,SigningReason?:string,Location?:number,SigningLocation?:string}} [init] */
    constructor(init) { Object.assign(this, init) }
    /** @type {string} */
    ClientKey;
    /** @type {string} */
    AuthorizationID;
    /** @type {string} */
    UserSSN;
    /** @type {number} */
    DocumentId;
    /** @type {string} */
    Message;
    /** @type {string} */
    SigningReason;
    /** @type {number} */
    Location;
    /** @type {string} */
    SigningLocation;
}

JavaScript SignDocumentPDF DTOs

To override the Content-type in your clients, use the HTTP Accept Header, append the .other suffix or ?format=other

HTTP + OTHER

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

POST /SignDocumentPDF/{ClientKey} HTTP/1.1 
Host: imzagerservices.eyyubiye.bel.tr 
Accept: text/jsonl
Content-Type: text/jsonl
Content-Length: length

{"ClientKey":"String","AuthorizationID":"String","UserSSN":"String","DocumentId":0,"Message":"String","SigningReason":"String","Location":0,"SigningLocation":"String"}

HTTP/1.1 200 OK
Content-Type: text/jsonl
Content-Length: length

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