Upload a handwritten signature

POST /api/account/senders/{senderId}
payload:
{
    "signature": {
        "handdrawn": "your handdrawn value",
        "textual": null
    }
}

{
   "id":"signer1ID",
   "type":"SIGNER",
   "index":0,
   "signers":[
      {
         "language":"en",
         "signature":{
            "textual":null,
            "handdrawn":"your handdrawn value"
         },
         "id":"signer1ID",
         "company":"ABC Bank",
         "email":"[email protected]",
         "firstName":"1.firstname",
         "lastName":"1.lastname",
         "title":"CEO",
         "created":"2018-08-08T15:16:22Z",
         "address":null,
         "name":""
      }
   ],
   "name":"Signer1"
}

GET /api/account/senders/{senderId}/apiKey 
Authorization: account owner's apiKey

using Silanis.ESL.SDK;
var code = new ImageConverter().convertImage("yourpath\\test1.png", 0);

HI, am struggling to make the sig upload work using .Net Sdk rather than REST.  Is this doable?  

Hi Chris,

Thanks for your post! And could you elaborate a bit more about your use case? Are you introducing this capability to your application, or it's just an one time operation? Are you uploading hand-drawn signatures to your sender profiles so that the captured signatures are stored and reused in any subsequent transactions, or specific signers during a package creation? 

In general, there's known limitations in .NET SDK in regards to uploading handdrawn, so very likely you will still have to create a hybrid style combing SDK and RESTful code. If you can share more background information, I would create some sample codes to facilitate your integration.

Duo

Thanks for the quick reply!  Our (Blazor) app presents the doc to be signed in an Iframe.  We we have signature graphics on file for all our potential signers, and we just wanted that to appear when they click to sign.  Hunted hard for .Net Sdk that exposed the part of the payload we'd need to build.  Generally SDk is just a convenience for us in C#, so Rest is not too bad if we have to go that way.  Do you have a nice API Models lib for C#?

Hi Chris,

Here you go! I've made an example including a simplified API modelling with the most commonly used properties. I also leveraged Newtonsoft to serialize the object. Although it's a simplified API modelling, it's very easy to extend it based on your requirement.

On top of that, not sure whether you are currently developing with New Signer Experience. We've found that turning on New Signer Experience could affect the existing integrations which involves uploading signer hand-drawn signatures, and is actively reporting it to R&D team. I will follow up with the existing cases and even create a new support ticket on your organization's behalf if it's necessary.

Duo

Awesome, thank you.  You actually hit right on my next question...that being the new UI experience.  Not really related to this topic, but pretty sure we are using the old one.  Our contract "kicks in" in a few weeks, so doing our sandbox deving now.  Could you kindly direct me to how I ask to have the New turned on?  Thanks again. 

Hi Chris,

If you simply want to turn on the feature, you can contact support team([email protected]).

Otherwise if you needs extra layout, string customizations, you can choose to fill in a branding form (https://apps.esignlive.com/ft?token=WldmQ3d3T3J1Mi14WFhpUTZ2aF92Vms5STR3PSZmYWxzZQ), after selecting your options and completing signing this form, it automatically creates you a support ticket.

Duo

Than you, sir.  Cheers.