Tagged: 

This topic contains 9 replies, has 2 voices, and was last updated by  sudhangi 1 day, 2 hours ago.

  • Author
    Posts
  • Participant
    sudhangi
    Regular Member
    Member since: 01.12.2015
    Number of posts: 43

    HI,
    Is it possible to get the api key of the sender who sent the package.
    Thank you,
    Sudhangi

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

    Score

    0

    Hi Sudhangi,

    This question has already been answered in a previous post: https://developer.esignlive.com/forums/topic/how-to-get-senders-apikey-via-api/


    Haris Haidary
    eSignLive Technical Evangelist
    Participant
    sudhangi
    Regular Member
    Member since: 01.12.2015
    Number of posts: 43

    Score

    0

    Hi Harris,
    Let me try that. I will get back to you.
    Thanks a bunch,
    Sudhangi

    Participant
    sudhangi
    Regular Member
    Member since: 01.12.2015
    Number of posts: 43

    Score

    0

    Hi Harris,
    I see that the only way to get api key for a sender is through eSL API.
    on another note is there any information that you can share with me about the difference between eSL Java SDK features/functions and eSL API features/functions.
    Thans,
    Sudhangi

    Keymaster
    Haris
    Jedi Master
    Member since: 05.11.2015
    Number of posts: 1134
    Approved answer

    Score

    0

    Essentially, the SDKs take away a lot of the work you’ll need to do compared to going through REST. Work such as building the json payload, httpclient, defining the headers, etc.. It is very powerful and easy way to get started with eSignLive. However, through REST, you have a lot more flexibility. Anything you can do with the SDKs you can do in REST. However, the reverse is not true (e.g. getting sender api key). You can have a look at our feature guides and documentationfor a list of all the calls available through the SDKs and REST.


    Haris Haidary
    eSignLive Technical Evangelist
    Participant
    sudhangi
    Regular Member
    Member since: 01.12.2015
    Number of posts: 43

    Score

    0

    Hi Harris,
    The URL mentioned in the documentation is https://sandbox.esignlive.com/api/
    For FedRAmp instance we use the URL https://signer-sandbox-gov.esignlive.com/api
    So to retrieve the senders for FedRamp sandbox will the url be : https://signer-sandbox-gov.esignlive.com/api/account/senders?from=0&to=100” ?

    Thanks,
    Sudhangi

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

    Score

    0

    Yes, that is correct.


    Haris Haidary
    eSignLive Technical Evangelist
    Participant
    sudhangi
    Regular Member
    Member since: 01.12.2015
    Number of posts: 43

    Score

    0

    Ok so I was successfully able to retrieve the senders using “https://signer-sandbox-gov.esignlive.com/api/account/senders?from=0&to=100”

    But when I try to retrieve the api key for a specific sender (eg: “https://signer-sandbox-gov.esignlive.com/api/account/senders/{senderId}/apiKey”) it give me a 404 response.

    Any idea what would be the problem here ?

    Sample Code snippet looks like this(Using JAX-RS Client):
    Client client2 = ClientBuilder.newClient();
    WebTarget ret2 =client2.target(“https://signer-sandbox-gov.esignlive.com/api/account/senders/xxxxx/apiKey”);
    client2.configuration
    Response response2 = ret2.request(MediaType.APPLICATION_JSON).header(HttpHeaders.AUTHORIZATION, “Basic ” + “xxxxxxxxxxx==”).get();
    System.out.println(“response2:” + response2.toString());

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

    Score

    0

    Make sure you have the correct sender id as a 404 error means that the resource is not found (i.e. target url not valid or in this case most likely the sender id is wrong).


    Haris Haidary
    eSignLive Technical Evangelist
    Participant
    sudhangi
    Regular Member
    Member since: 01.12.2015
    Number of posts: 43

    Score

    0

    Yeah you are right.
    The id value was incorrect.
    Thanks a bunch
    -Sudhangi

You must be logged in to reply to this topic.