ImzagerServices

SignContentV2

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

namespace DaB.Imzager.Services.ServiceModel

open System
open System.Collections
open System.Collections.Generic
open System.Runtime.Serialization
open ServiceStack
open ServiceStack.DataAnnotations

    [<AllowNullLiteral>]
    type SignContentResponse() = 
        member val Result:Boolean = new Boolean() with get,set
        member val ServiceSuccessResult:Boolean = new Boolean() with get,set
        member val ErrorMesage:String = null with get,set
        member val Content:Byte[] = [||] with get,set

    [<AllowNullLiteral>]
    type SignContentV2() = 
        member val ClientKey:String = null with get,set
        member val AuthorizationID:String = null with get,set
        member val UserSSN:String = null with get,set
        member val Content:Byte[] = [||] with get,set
        member val SignerSSN:String = null with get,set
        member val SignerEMail:String = null with get,set
        member val SignMessage:String = null with get,set

F# SignContentV2 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 /SignContentV2/{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","Content":"AA==","SignerSSN":"String","SignerEMail":"String","SignMessage":"String"}

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

{"Result":false,"ServiceSuccessResult":false,"ErrorMesage":"String","Content":"AA=="}