DocuSign eSign RestApi Chunked上传

本文介绍了DocuSign eSign RestApi Chunked上传的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

我对 ChunkedUploads 有疑问。

目前，我正在为该帖子寻求解决方案：

Currently I am working on the solution for this post:

DocuSign API信封创建超时

谁能解释如何分块发送 EnvelopeDefinition 吗？

Can anyone explain how to send an EnvelopeDefinition in chunks ?

当前我呼叫：

var request = new ChunkedUploadRequest() { Data = <how to put the envelopeDefinition content here?> }; var response = envelopesApi.CreateChunkedUploadAsync( ApiAccountId, request );

编辑

我试图理解如何将EnvelopDefinition对象包装到ChunkedUploadRequest对象中。

I am trying to understand how to wrap an EnvelopDefinition object into a ChunkedUploadRequest object.

尽可能简单：ChunkedUploadRequest对象的data属性应该是什么样？数据应包含什么？ 我在官方的eSignature文档中找不到关于此主题的任何详细说明： docs.docusign/esign/restapi/Envelopes/ChunkedUploads/create/#/definitions/chunkedUploadRequest

As simple as possible: What should the data property of the ChunkedUploadRequest object look like? What should the data contain? I cannot find any detailed explanation on the subject in the official eSignature documentation: docs.docusign/esign/restapi/Envelopes/ChunkedUploads/create/#/definitions/chunkedUploadRequest

推荐答案

您将base64（我尝试使用base64）字符串分成多个部分，每个部分都是一个序列。然后是API调用序列：

You break the base64 (I tried with base64) string into multiple parts, each part is a sequence. Then below are the API calls seq:

• 创建ChunkUpload - POST / v2 / accounts / {accountId} / chunked_uploads ，这将返回 chunkedUploadId 和 chunkedUploadUri 。 chunkedUploadId 将用于来进行更多与chunkupload相关的调用，例如更新块上的更多流或提交chunkupload。 chunkedUploadUri 将用于在创建信封调用中添加文档的，在 document节点内的remoteUrl中将其引用为。

• Create ChunkUpload - POST /v2/accounts/{accountId}/chunked_uploads, this returns the chunkedUploadId and chunkedUploadUri. chunkedUploadId will be used for more chunkupload related calls, like update more stream on the chunk or for committing the chunkupload. chunkedUploadUri will be used to add document in the create envelope call, it will be referred in remoteUrl inside "document" node.

响应如下：

{ "chunkedUploadId": "C4AE9DF7-E3E4-4F3F-B419-29F59647D860", "chunkedUploadUri": "docusignchunkedupload://C4AE9DF7-E3E4-4F3F-B419-29F59647D860", ... }

• 然后 PUT / v2 /帐户/ {accountId} / chunked_uploads / {chunkedUploadId} / {chunkedUploadPartSeq} 需要调用才能上载base64的剩余部分文档（字符串的其他部分）。顺序会像 1,2,3等

  • Then PUT /v2/accounts/{accountId}/chunked_uploads/{chunkedUploadId}/{chunkedUploadPartSeq} call is required to uploaded remaining part of the the base64 document (other part of the string). Sequence will increase like 1,2,3 etc

    最终 Chunk Commit 调用一样增加， PUT / v2 / accounts / {accountId} / chunked_uploads / {chunkedUploadId} 使此块中的可全部用于创建信封调用文档的块已添加。

    Finally Chunk Commit call, PUT /v2/accounts/{accountId}/chunked_uploads/{chunkedUploadId} to make this Chunk available to be used in create envelope call once all the chunk of a document is added.

    在创建信封调用中，您将请参阅下面的块

    In Create envelope call, you will refer to chunk as below

    Envelope Definition's document will look like below "documents": [{ "remoteUrl": "docusignchunkedupload://C4AE9DF7-E3E4-4F3F-B419-29F59647D860", "documentId": "1", "name": "Test"

    }

    `remoteUrl` is the `chunkedUploadUri` returned in the first call.