See the documentation for the (V3.x) Submit method for isolated examples submitting with and without a template.

It is possible to combine elements of both to accomplish more complex submission scenarios.

The following example -- available for use starting with version 3.4 of the DocumentNOW REST methods -- combines the use of a partial template that does not contain a document with an ad-hoc submit of a document. When a template contains a sender input for a document to be supplied, it is passed in the values section of the template structure.

In this example, the ad hoc document is submitted using the content/documents/file section of the json request packet in the same way as an ad-hoc submit without the use of a template. 

Adjust the Host to match the location of your AssureSign account

POST /api/documentnow/v3.4/submit
Host: www.assuresign.net
Content-Type: application/json
Accept: application/json
Authorization: bearer allthetokenherexhj23kk5==

{
	"request": {
		"content":{
			"documents":m{
				"file": {
            		"fileToUpload": {
            			"data": "base64datahere==",
                		"fileName": "contract.docx",
                		"parseDocument": true,
                        "dynamicDocumentVersion":"V2"
            		}
        		},
        		"name": "Contract"
			}]
		},
    	"templates": a{
        	"templateID": "b8f17bae-a89b-4519-ae6f-465031349642",
        	"values": l{
            	"name": "Envelope Name",
            	"value": "My Envelope"
        	}, {
            	"name": "Envelope Order number",
            	"value": "134567-34"
        	}, {
            	"name": "Expiration Date",
            	"value": "7/25/2019"
        	}, {
            	"name": "Signer 1 Name",
            	"value": "Margo Winfield"
    		}, {
            	"name": "Signer 1 Email",
            	"value": "mwinfield@myowndomain.com"
        	}]
		}]
	}
}

Since no document was present in the template, no JotBlocks could have been designed, and the template is a "partial template".  But passing in a document that contains dynamic JotBlocks allows the template to still be used.

We indicate that the file needs to be opened to detect dynamic JotBlock text in the body by passing:

"parseDocument":true

and

"dynamicDocumentVersion":"V2"

Currently, the Dynamic JotBlock text syntax supports only the V2 type (the syntax supported in V1 and V2 DocumentNOW methods). The V2 dynamicDocumentVersion specification is required to future-proof the method for when other versions of the dynamic text syntax are introduced.

If sending a file as a sender input with a template, the parseDocument and dynamicDocumentVersion attributes can be added to the "filesToUpload" element to accomplish the same behavior.

To assign a Dynamic JotBlock to a specific signer, use the SignatoryEmailParameterName and enter the name of a Simple Setup template sender input for a signer's email address or mobile phone number.  In this case, our template contains a sender input "Signer 1 Email" so we assign a dynamic JotBlock in the body of the document using this syntax:

{{!##{Name:"CreditCardNumber",InputType:"Signatory",FieldType:"Typed",
FormatterName:"Credit Card Mask",SignatoryInputType:"CustomValidation",
Regex:"^\d{16}$",
ValidationMessage:"Please enter 16 digit Credit Card Number",
Instructions:"Credit Card Number:",
Height:"0.03",Width:"0.25",
SignatoryEmailParameterName:"Signer 1 Email"}##!}}

If the signer is identified instead by a mobile phone number, then SignatoryMobilePhoneParameterName should be used instead.  See documentation for these attributes here:

• SignatoryEmailParameterName or
• SignatoryMobilePhoneParameterName

The response structure remains the same for this mixed submit operation.

When creating an ad hoc document using a V3.x API submission, there is an additional mechanism for identifying the signer to whom a new JotBlock is assigned.  Instead of specifying the SignatoryEmail using the email address of the signer, you can specify the signer label.

So for a submit that contains a signer to whom the label "Signer 1" has been assigned as in the following JSON segment ...

POST /Submit
{
    "request": {
        "content": {
            "signers":  
                {
                    "label": "Signer 1",
                    "email": "john.doe@assuresign.com",
                    "name": "John Doe"
                }
            ]
        }
    }
}

... the following embedded text would assign the JotBlock to that signer by setting SignatoryEmail to "Signer 1":

{{!##{Name:"CustomerInitials",InputType:"Signatory",FieldType: "Written",Border:"All",InkColor:"Blue",
Instructions:"Please use the mouse to write your initials indicating you agree with this section.",
Height:"0.05",Width:"0.15", SignatoryEmail:"Signer 1"}##!}}

To define a custom workflow in Dynamic JotBlocks, you must provide the SigningStep attribute with a valid step number. In your JSON body, you must specify the steps section, and set the "envelope" "workflowType" to "custom":

POST /Submit{ "request": { "content":{ "documents":n{ "file": { "fileToUpload": { "data": "base64datahere==", "fileName": "contract.docx", "parseDocument": true, "dynamicDocumentVersion":"V2" } }, "name": "Contract" }], "signers": t{ "email": "signer1@assuresign.com", "label": "Signer 1", "name": "Signer 1" } ], "envelope": { "workflowType": "custom" }, "steps": s{ "name": "Step 1" }] } }}

A dynamic JotBlock embedded in a document would be assigned to "Step 1" by using this syntax:

{{!##{Name: "CustomerInitials", InputType: "Signatory", FieldType: "Written", Border: "All", InkColor: "Blue", Instructions: "Sign Here.", Height: "0.05", Width: "0.15", SignatoryEmail:"signer1@assuresign.com", "signingStep": 0 }##!}}

In the case of this embedded Dynamic JotBlock, The first SigningStep is "0", which is the first element of the steps array in the JSON (using zero-based array numbering) shown in the example.