You're seeing just the function views_post_envelope_sender_view, go back to DocuSign.Api.EnvelopeViews module for more information.
Link to this function

views_post_envelope_sender_view(connection, account_id, envelope_id, opts \\ [])

View Source


) :: {:ok, DocuSign.Model.EnvelopeViews.t()} | {:error, Tesla.Env.t()}

Returns a URL to the sender view UI. Returns a URL that enables you to embed the sender view of the DocuSign UI in your applications. The returned URL can only be redirected to immediately after it is generated. It can only be used once. Therefore, request the URL immediately before you redirect your user to it. For the best user experience, don't use an iFrame. For iOS devices DocuSign recommends using a WebView. Multiple solutions are available for maintaining your client state. See the "Maintaining State" section of the Embedded Signing introduction. After the user has completed the sending view, their browser is redirected to the `returnUrl` you supplied. By default, if the envelope already contains one or more documents, DocuSign will initially show the document tagging view when you redirect to the URL. To start with the envelope's recipients and documents view instead, examine the URL in the method's response. Then change the query parameter from `send=1` to `send=0` to start with the recipients/documents view.


  • connection (DocuSign.Connection): Connection to server
  • account_id (String.t): The external account number (int) or account ID Guid.
  • envelope_id (String.t): The envelope's GUID. Eg 93be49ab-afa0-4adf-933c-f752070d71ec
  • opts (KeywordList): [optional] Optional parameters
    • :return_url_request (ReturnUrlRequest):


} on success {:error, info} on failure