Docusign Create Recipient View Url

• emailstring
  Email address of the recipient. Use either `email` and `userName` or `userId` to identify the recipient.
• userIdstring
  User ID of the recipient. Use either the user ID or email and user name to identify the recipient. If used with clientUserId, must match a recipientId.
• pingUrlstring
  Client URL that DocuSign pings to indicate signing is active, allowing the client to reset its session timer.
• userNamestring
  Username of the recipient. Use either `email` and `userName` or `userId` to identify the recipient.
• accountIdstring
  The external account number (int) or account ID GUID. This is a required path parameter that identifies the DocuSign account associated with the envelope.
• returnUrlstring
  URL to redirect after the signing session ends (max 470 characters). Include 'https://' to avoid redirection issues. DocuSign adds an 'event' query parameter indicating the outcome (e.g., signing_complete, cancel, decline).
• envelopeIdstring

  Required
  The ID of the sent envelope for which to create the recipient view. This is a required path parameter that uniquely identifies the envelope in the DocuSign system.
• assertionIdstring
  A unique identifier of the authentication event executed by the client application.
• recipientIdstring
  Unique identifier for the recipient. Used by tabs to indicate which recipient should sign the document.
• clientUserIdstring
  A sender-created value for embedded (captive) recipients. Use your application's client ID (user ID) for the recipient to connect authentication details to the signature. Maximum length: 100 characters.
• displayFormatstring
  Display format for the embedded view (e.g., 'focused' or 'default').
• pingFrequencystring
  Interval in seconds between pings on the pingUrl (default: 300). Valid values: 60-1200 seconds.

• data

  Required
  Data from the action execution
• errorstring
  Error if any occurred during the execution of the action
• successfulboolean

  Required
  Whether or not the action execution was successful or not

No verified related use cases are linked yet.

No published Skills explicitly reference this Action yet.