Dan4560

Post Package default sender information update

0 votes

Hi,

After creating a package with the POST Package call, a default sender is set. Is it possible to update the default sender's information? 

One method that somewhat works is using the following:
"roles": [
        {
            "type": "SENDER",
            "signers": [
                {
                    "firstName": "John",
                    "lastName": "Doe",
                    "email": "[email protected]"
                }
            ],
            "name": "Sender1"
        }

],
However the above only updates the default sender first/last name and not the associated email. Is this working as intended or a bug since following the same schema works with creating a new signers information.

We have also tried updating the package with a PUT api/packages/{packageID}/roles/{roleID} where roleID is the role ID of the SENDER.

 

  "signers": [
                {
                    "firstName": "John",
                    "lastName": "Doe",
                    "email": "[email protected]",
                    "id": "AssoicatedRoleID"

                }

Although this appears to update all the information and returns no errors from the API call, when trying to move onto the design step from the web platform we get the following:
missing translation: en.esl.error.notFound.roleNotFoundForSignerId
 


Reply to: Post Package default sender information update

0 votes

Hi Dan4560,

 

Thanks for your post!

First of all, it's a general limitation that you can't update sender email once a transaction/package has been created (once you received the package ID). You'd have to delete and recreate another transaction instead.

If you want to use a different sender email than the API Key/Token holder, in your package creation API, you can either (1) specify sender email (and optionally firstname and lastname) at "sender" node like below example JSON does, (2)or like you mentioned, explicitly add the sender as a signer and specify type as "SENDER".

{
  "roles": [
    {
      "id": "Role1",
      "signers": [
        {
          "email": "[email protected]",
          "firstName": "1.firstname",
          "lastName": "1.lastname",
          "company": "OneSpan Sign"
        }
      ]
    }
  ],
  "documents": [
    {
      "approvals": [
        {
          "role": "Role1",
          "fields": [
            {
              "page": 0,
              "top": 100,
              "subtype": "FULLNAME",
              "height": 50,
              "left": 100,
              "width": 200,
              "type": "SIGNATURE"
            }
          ]
        }
      ],
      "name": "Test Document"
    }
  ],
  "name": "Example Package",
  "type": "PACKAGE",
  "language": "en",
  "emailMessage": "",
  "description": "New Package",
  "autocomplete": true,
  "sender": {
    "email": "your_sender_email",
    "firstName": "John",
    "lastName": "Smith"
  },

  "status": "SENT"
}

 

Duo

 

Duo Liang OneSpan Evangelism and Partner Integrations Developer


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