Actions198
- Account Custom Field Actions
- Account Group Actions
- Account Settings Actions
- Account Signature Actions
- Account User Actions
- Account Watermark Actions
- Billing Actions
- Brand Actions
- Bulk Send Actions
- Captive Recipient Actions
- Chunked Upload Actions
- Cloud Storage Actions
- Comments Actions
- Composite Template Actions
- Connect Configuration Actions
- Connect Event Actions
- Consumer Disclosure Actions
- Contact Actions
- Custom Tab Actions
- Diagnostics Actions
- Document Generation Actions
- Email Archive Actions
- Envelope Actions
- Envelope Purge Actions
- Envelope Attachment Actions
- Envelope Custom Field Actions
- Envelope Document Field Actions
- Envelope Email Setting Actions
- Envelope Lock Actions
- Envelope Notification Actions
- Envelope Transfer Actions
- Folder Actions
- ID Verification Actions
- Notary Actions
- Notary Journal Actions
- Payment Tab Actions
- Permission Profile Actions
- PowerForm Actions
- Recipient Tabs Actions
- Reporting Actions
- Scheduled Routing Actions
- Signing Group Actions
- Supplemental Document Actions
- Template Actions
- Template Bulk Recipient Actions
- Template Custom Field Actions
- Template Document Actions
- Template Lock Actions
- Template Notification Actions
- Template Recipients Actions
- Template View Actions
- Trust Service Provider Actions
- Workspace Actions
- Organization Actions
Chunked Upload → Initiate
AI-generatedSummary
Starts a DocuSign chunked upload session for a large document by declaring its MIME type and total size in bytes. The session is then used with the Upload Chunk and Commit operations of the same resource.
Inputs
- authentication — Authentication method: JWT (Service Integration, the default) or OAuth2 (User Authorization).
- contentType (required) — MIME type of the document to be uploaded. Defaults to application/pdf.
- totalSize (required) — Total size of the document in bytes. Defaults to 0, so set it to the real file size.
Output shape
A single JSON item containing the DocuSign API response for the new chunked upload session. This is expected to include the chunked upload ID, which later Upload Chunk and Commit steps need.
The source pack shows only a stub for the handler (handleChunkedUploadInitiate), not its body. The exact endpoint and response fields are therefore not verified here. Requests use the node's shared retry logic, with backoff on rate limits and 5xx errors.
Examples
Example 1: Upload a 50 MB PDF contract that is too large for a single request.
Resource: Chunked Upload, Operation: Initiate, Content Type: application/pdf, Total Size: 52428800. Pass the returned upload ID to Upload Chunk, then Commit.