man1van's account

I tried with a JSON that looks something like the below with a field named [Signer1.Capture1] to extract signature field. The create package works but when I try retrieving the signing url it gives back an unexpected error. Not sure what is the issue. { "roles":[ { "id":"Signer1", "type":"SIGNER", "index":0, "signers":[ { "firstName":"Signer", "lastName":"1", "email":"[email protected]", "language":"en", "title":"" }], "name":"Signer1" }], "documents":[ { "approvals":[ { "role":"Signer1", "fields":[ { "id":"[Signer1.Capture1]", "page":0, "subtype":"CAPTURE", "extract":true, "type":"SIGNATURE" }], "name":"[Signer1.Capture1]" }], "name": "Test File" }], "name": "Test Package REST", "type":"PACKAGE", "language":"en", "description":"New Package", "autoComplete":true, "status":"SENT" }

Thanks. Can I setup multiple API keys under a same account ?

Thanks Haris. When we receive a call back we should be able to route it to appropriate Sender. On option I could think of is for us to get the package based on package id and then introspect the sender to identify the sender for routing. Are there other options ? I'm looking for an option where in the Sender is identified as part of the callback so that I do no have to make an additional call to get package.

Sounds good. Thanks.