Hello I have one question, for the designer session the package Id that we need must be from the Transaction for a Sender, or it can be a package id from a normal transaction.
January 21Created
January 21Last Updated
2 years agoLast Reply
3Replies
30Views
2Users
0Likes
0Links
Duo_Liang | Posts: 3776
Reply to: Designer Viewr
Friday, January 21, 2022 at 01:05pm
0
votes
Hi saida.higuera,
Thanks for your post! Below is the formula of a designer URL:
Note here the parameter is "senderAuthenticationToken", in this case, the package ID can only be the ID when you retrieved this sender authentication token:
POST /api/authenticationTokens/sender
{
"packageId":"Nw7q_VpnEcqQ-0ySHvTl6vho-sU="
}
Alternatively, if you retrieve the user authentication token, and use parameter "authenticationToken" instead, you can build this link with any package ID that was created by this user:
Ok thank you for the information. Just to clarify:
I understand with your answer that the same packageID that I ues here: https://sandbox.esignlive.com/auth?senderAuthenticationToken={senderToken}&target=https://sandbox.esignlive.com/a/transaction/{packageId}/designer, has to be the same package id that we use to get the senderAuthenticationToken.
now the question is can i have a senderAuthenticationToken with a any package ID or it has to be with a packageID of a Sender transaction.
You can only retrieve the sender authentication token if:
#1 you are authenticating the API call with an API Key/Token of an admin user (depending on if your account has "Roles & Permissions" feature turned on, you will need different settings to make sure the admin user has sufficient permissions, we can talk about this later)
#2 the transaction/package was created by a sender under your account (In this sense, it's more close to "sender transaction" I believe)
Reply to: Designer Viewr
Friday, January 21, 2022 at 01:05pmHi saida.higuera,
Thanks for your post! Below is the formula of a designer URL:
https://sandbox.esignlive.com/auth?senderAuthenticationToken={senderToken}&target=https://sandbox.esignlive.com/a/transaction/{packageId}/designer
Note here the parameter is "senderAuthenticationToken", in this case, the package ID can only be the ID when you retrieved this sender authentication token:
POST /api/authenticationTokens/sender
{
"packageId":"Nw7q_VpnEcqQ-0ySHvTl6vho-sU="
}
Alternatively, if you retrieve the user authentication token, and use parameter "authenticationToken" instead, you can build this link with any package ID that was created by this user:
https://sandbox.esignlive.com/auth?authenticationToken={userAuthToken}&target=https://sandbox.esignlive.com/a/transaction/{packageId}/designer
Duo
Reply to: Designer Viewr
Monday, January 24, 2022 at 10:40amOk thank you for the information. Just to clarify:
I understand with your answer that the same packageID that I ues here: https://sandbox.esignlive.com/auth?senderAuthenticationToken={senderToken}&target=https://sandbox.esignlive.com/a/transaction/{packageId}/designer, has to be the same package id that we use to get the senderAuthenticationToken.
now the question is can i have a senderAuthenticationToken with a any package ID or it has to be with a packageID of a Sender transaction.
Reply to: Designer Viewr
Monday, January 24, 2022 at 10:52amHi saida.higuera,
You can only retrieve the sender authentication token if:
#1 you are authenticating the API call with an API Key/Token of an admin user (depending on if your account has "Roles & Permissions" feature turned on, you will need different settings to make sure the admin user has sufficient permissions, we can talk about this later)
#2 the transaction/package was created by a sender under your account (In this sense, it's more close to "sender transaction" I believe)
Duo