1

I'm using the Docusign REST API to create envelopes, then I call the POST Recipient View method to generate the recipient view.

The documentation indicates:

You can use with userId or email and userName to identify the recipient. If userId is used and a clientUserId is provided, the userId must match a recipientId (which can be retrieved with a GET recipients call) for the envelope.

I know for sure userName can change if the user types a different full name when adopting the signature, so I'm favoring userId. As suggested in that documentation I call GET recipients right after creating the envelope, and I store all the userId guids.

Later, when the recipient is ready to sign and I call POST Recipient View I send the userId I saved earlier and the clientUserId (because it's an embedded recipient). Most of the times it works, but sometimes I get an error:

{
"errorCode": "INVALID_REQUEST_PARAMETER",
"message": "The request contained at least one invalid parameter. A value was not found for parameter 'userName'."
}

When that happened the first time I called GET Recipients for that failed envelope and I noticed the userId I captured when the envelope was created doesn't match the current userId.

My workaround is to call GET Recpients, get the current userId, and call POST Recipient View again. That's not ideal.

Questions/comments:

  • Is userId changing during the lifetime of an envelope?
  • What's the best practice to obtain the proper userId? Get it after creating the envelope? Get it right before creating the recipient view?
  • It would be great if the API returned the userIds in the response coming back when creating the envelope.
oscarmorasu
  • 901
  • 3
  • 11
  • 28
  • I'd have to see your request, but it appears that your request does not have 'userName' identified with a value when you're requesting the recipient token. – Andrew Jun 27 '14 at 19:16
  • I don't believe the userId is supposed to change once after the recipient has been added to the envelope, that might be a bug. How often do you encounter this? DocuSign's demo environment is a little less stable compared to production (www) environment, if this is indeed a bug I'd be willing to be it's only in demo and will be fixed soon (since that would be a bad one). – Ergin Jun 30 '14 at 23:37
  • I see it everyday for sure, but only on a small group of envelopes. This happens in prod. I don't hit demo often enough to see the error. If it helps I can provide the EnvelopeIds where this happened. – oscarmorasu Jun 30 '14 at 23:47
  • @oscarmorasu did you find answers to your questions and comments? – mackth Jun 13 '19 at 15:19

0 Answers0