harishkonda's account

Haris, Both headers are -- application/json. Can you also confirm, the URI would be /api/packages/{package_id}?

I am testing this internal to my work place, not on eSign sandbox.

I was sending the request payload in form-data, so it was changing content type header, but after looking at your screenshot, i changed it to raw, and it worked. Thanks a lot.

When you are creating the package, please make sure the status in request. If the status is as DRAFT, then you wont get any email notifications nor the package wont show in Inbox. You have to specify the package status as SENT either creation time or later when package is ready as per your requirements. Then Signers will start getting email notifications.

Signing URL does not expire and thats the advantage over the session token. You can read about it in this article - https://developer.esignlive.com/guides/feature-guides/signing-url/ When you say, is it configurable? what way you are expecting? The API response itself is so easy, it already frames a URL for you and give it, not sure about your requirement, but I do not see the necessity to have it as configurable item.