detroyer | Posts: 35

Sender Token

Wednesday, November 2, 2016 at 06:37am
0 votes
Is this sender token required in a json package? I ask because I get an error sending a package request stating "id": "sender" not found. This is just a sender not requiring a signature but sending a request package for signature of another user. From this request, I would get a package id and then initiate another request to obtain a signer session token passing this packageid and signerid. Neither user has an account with eSign, not using UI. This is all done through REST API. "sender": { "company": "Sender Company", "email": "[email protected]", "id": "sender", "status": "ACTIVE", "type": "REGULAR" },
Approved Answer
harishaidary | Posts: 1812

Reply to: Sender Token

Wednesday, November 2, 2016 at 07:22am
0 votes
In esignlive, senders are responsible for creating and sending packages to be signed. Hence, senders need to have an account in esignlive. The error you are getting is because you are trying to send a package from a sender that isn't present in your account. Also, the "sender" object field in the json is not required when creating packages (btw there is no "id" field the "sender" object). Though, if you omit it, it will send from your own account. Here are a couple of links that you can go through that will help you better understand the functionality of senders: http://docs.esignlive.com/content/c_integrator_s_guide/sdk/g_managing_accounts_and_groups/managing_accounts.htm https://developer.esignlive.com/guides/feature-guides/senders/

Hello! Looks like you're enjoying the discussion, but haven't signed up for an account.

When you create an account, we remember exactly what you've read, so you always come right back where you left off

LoginSign Up