This topic contains 2 replies, has 3 voices, and was last updated by  harishkonda 1 week, 4 days ago.

  • Author
    Posts
  • Participant
    wbass
    Newbie
    Member since: 05.06.2017
    Number of posts: 10

    I have been trying to wait to ask more questions and consolidate them in one post for you. Your welcome. 🙂

    Regarding the iframe/inperson signing ceremony. In the package API that we send to eSignLive to create the signing ceremony iframe, is an email address for each signer required?

    Edit (mwilliams): Other questions moved to a separate post.

    Questions about the Evidence Summary

    Keymaster
    mwilliams
    Guru
    Member since: 21.08.2015
    Number of posts: 773

    Score

    0

    Hey wbass,

    When creating the actual transaction, you must give everyone an email address, even for an in-person transaction.

    When actually getting the in-person signing ceremony session token to embed in an iframe, you do not need to get a token for each signer.

    Hope this helps! 🙂


    – Michael
    eSignLive by VASCO | Partner and Developer Technologies Manager
    Facebook – https://www.facebook.com/michael.williams1120
    Twitter – https://twitter.com/mwilliams1120
    LinkedIn – https://www.linkedin.com/in/mwilliams1120
    Participant
    harishkonda
    Member
    Member since: 01.03.2017
    Number of posts: 22

    Score

    0

    Hey Mike,
    In this article, the resource URI for Token API is different than the article I am referring to.

    I am referring to is, http://docs.esignlive.com/content/c_integrator_s_guide/rest_api/authentication_tokens.htm

    Can you please confirm, what is the latest API we need to go through?

    Is their API page for eSign, where it lists every available feature with documentation other than the Feature Guides?

    Thanks for your help.

You must be logged in to reply to this topic.