This topic contains 8 replies, has 2 voices, and was last updated by  Haris 5 months, 2 weeks ago.

  • Author
    Posts
  • Participant
    neelsp
    Senior Member
    Member since: 02.02.2016
    Number of posts: 75

    Hi,

    We are using the following API to retrieve the signer signing url
    GET /packages/{packageId}/roles/{roleId}/signingUrl

    We are controlling the signing process from within our host application by providing the signing url to the signer as an iframe within our application. For this to work effectively, we would like to disable the email that goes out to the signer at the package level.

    Please let us know if this is doable. (NOTE: we are creating the package using eSL apis)

    thanks
    Neel

    Keymaster
    Haris
    Jedi Master
    Member since: 05.11.2015
    Number of posts: 1450

    Score

    0

    Hi Neel,

    Yes it is possible. You will need to send an email to support to have it disabled.

    support@esignlive.com


    Haris Haidary
    OneSpan Technical Consultant
    Participant
    neelsp
    Senior Member
    Member since: 02.02.2016
    Number of posts: 75

    Score

    0

    Hi Haris,

    So just to reconfirm, the support team will be able to tell us how to disable the signer email at the package level …right?
    Please note that we are NOT looking to disable it at the account level.

    thanks
    Neel

    Keymaster
    Haris
    Jedi Master
    Member since: 05.11.2015
    Number of posts: 1450

    Score

    0

    Neel,

    What you’ll looking to do is disable the activation email but keep the notify email feature enabled. Hence, you can control when signers receives the email notification from esignlive. https://developer.esignlive.com/guides/feature-guides/notify-signers/


    Haris Haidary
    OneSpan Technical Consultant
    Participant
    neelsp
    Senior Member
    Member since: 02.02.2016
    Number of posts: 75

    Score

    0

    So, here is our scenario…

    1) we create a package in esignlive using the esignlive api
    2) Once the package is created, esignlive sends out email the signers for initiating the signing ……This is what we do not want to happen

    We want to control the signing process from within our application UI by displaying the signing url from within our application iframe.

    So, we want to be able to disable the default email that gets sent out in step 2) above

    Hope this clarifies.

    thanks
    Neel

    Participant
    neelsp
    Senior Member
    Member since: 02.02.2016
    Number of posts: 75

    Score

    0

    Hi Haris…any updates on this please?

    thanks
    Neel

    Keymaster
    Haris
    Jedi Master
    Member since: 05.11.2015
    Number of posts: 1450

    Score

    0

    Neel,

    Emails sent out by eSignLive are only configurable at the ACCOUNT level. Hence, if you want to disable the email being sent out to signers after package creation (called the activation email), you will need to send an email to support. Now, if you want to manage when to send out the email per package, you will need to use the notify signer feature (keep in mind you have the activation disabled here), which will send out an email to the signer after you’ve made the following API CALL:

    POST /api/packages/{packageId}/roles/{roleId}/notifications

    Does that make sense?


    Haris Haidary
    OneSpan Technical Consultant
    Participant
    neelsp
    Senior Member
    Member since: 02.02.2016
    Number of posts: 75

    Score

    0

    Thanks Haris for your response.

    Please note that we’ve users accessing the UI directly for adhoc use cases and we’ve scenarios where we are using the API route.

    Would the disabling the activation email at the account level apply to the adhoc usage too? Our requirement is to control the activation email only for the API route.

    thanks
    Neel

    Keymaster
    Haris
    Jedi Master
    Member since: 05.11.2015
    Number of posts: 1450

    Score

    0

    Unfortunately, that is not possible. Your only option would be to create a new account for the adhoc use case.


    Haris Haidary
    OneSpan Technical Consultant

You must be logged in to reply to this topic.