r-mikolajuk's account

Thank you Michael Indeed I was trying to update package with the roles at once. Using dedicated role endpoint API works better. But there is one issue - data is not merged but replaced with the defaults. In my case, there is only one signer so I'll go with other option - not setting emailMessage for Signer role at all, then update it on package level. That works just fine (for my case). Note about using

https://sandbox.esignlive.com/a/api/packages/{packageId}/roles/{roleId}

So I have a package (DRAFT), with Signer role:

{
  /* ... */
  "roles": [
    {
      /* ... */
      "type": "SENDER"
    },
    {
      "attachmentRequirements": [],
      "data": null,
      "emailMessage": {
        "content": "Hi Robert!"
      },
      "id": "e9536976-ca09-49e8-8eb3-13cc765bcbf6",
      "index": 0,
      "locked": false,
      "name": "Signer",
      "reassign": false,
      "signers": [
        {
          "address": null,
          "auth": {
            "challenges": [],
            "scheme": "NONE"
          },
          "company": "",
          "created": "2016-12-21T15:03:04Z",
          "data": null,
          "delivery": {
            "download": true,
            "email": true,
            "provider": false
          },
          "email": "[email protected]",
          "external": null,
          "firstName": "Robert",
          "group": null,
          "id": "Signer",
          "knowledgeBasedAuthentication": null,
          "language": "en",
          "lastName": "Last",
          "name": "",
          "phone": "",
          "professionalIdentityFields": [],
          "signature": null,
          "specialTypes": [],
          "title": "",
          "updated": "2016-12-21T15:03:04Z",
          "userCustomFields": []
        }
      ],
      "specialTypes": [],
      "type": "SIGNER"
    }
  ]
  /* ... */
}

Updating only the emailMessage content:

PUT /api/packages/2c8mpMd5QVm_ZYN6czx1ChzyJHE=/roles/e9536976-ca09-49e8-8eb3-13cc765bcbf6

{
    "emailMessage": {
        "content": "Signer only"
    }, 
    "id": "e9536976-ca09-49e8-8eb3-13cc765bcbf6"
}

Response I get (look at the fields list):

HTTP/1.1 200 OK
Cache-control: no-store, no-cache, must-revalidate
Connection: keep-alive
Content-Type: application/json
Date: Fri, 10 Feb 2017 08:02:36 GMT
Expires: Thu, 01 Jan 1970 00:00:00 GMT
P3P: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
Server: nginx
Transfer-Encoding: chunked
X-Powered-By: Undertow

{
    "attachmentRequirements": [], 
    "data": null, 
    "emailMessage": {
        "content": "Signer only"
    }, 
    "id": "e9536976-ca09-49e8-8eb3-13cc765bcbf6", 
    "index": 0, 
    "locked": false, 
    "name": "Signer1", 
    "reassign": false, 
    "signers": [], 
    "specialTypes": [], 
    "type": "SIGNER"
}

Get the package data:

{
  /* ... */
  "roles": [
    {
      /* ... */
      "type": "SENDER"
    },
    {
      "attachmentRequirements": [],
      "data": null,
      "emailMessage": {
        "content": "Signer only"
      },
      "id": "e9536976-ca09-49e8-8eb3-13cc765bcbf6",
      "index": 0,
      "locked": false,
      "name": "Signer1",
      "reassign": false,
      "signers": [],
      "specialTypes": [],
      "type": "SIGNER"
    }
  ],
  /* ... */
}

Result: trying to update only the emailMessage content I'm loosing signer data. Which, IMHO shouldn't work this way - it should work as it does on package level, where I can pass only that JSON:

{
    "emailMessage": "Just it"
}

If I'm using just the REST API I can remove the version at all?

Could it be somehow extended to the usual fields 4000 character limit?

This is quite odd explanation to me.

The reason behind is to keep the database size manageable.

So I can have a custom field with 4k characters limit, but can't have a message that long because of the database size?

The package and signer personal message should really be for very specific instructions to the signer, and not a generic way of displaying info.

Low field length limit doesn't help in keeping those instructions specific. It rather forces them to be general, short and not explanatory enough.