Reference

Action	Type	Endpoint
Create a Document	POST	/v1/documents/array
Uploading Files	POST	/v1/documents/{docID}/files.html
Updating and Sending a Document	PUT	/v1/documents/documents/{docID}/
Create Document Tags	PUT	/v1/documents/{docID}/tags/
Bulk Sign Using a Template	POST	/v1/templates/use/{docID}/
Retrieve Document	GET	/v1/documents/{docID}
List Documents	GET	/v2/documents/search2
Update Invitation List	PUT	/v1/documents/{docID}/invitations/
Get List of Invitees	GET	/v1/documents/{docID}/invitations/
Get List of Files	GET	/v1/documents/{docID}/files/
Delete File of a Document	DELETE	/v1/documents/{docID}/files/{fileID}

Callbacks

If you want Signority push the result to your server when the document is finalized, you need to set the document.documentSetting.postBackURL.
For example: Document.documentSetting.postBackURL = callback_URL/document_id
If the postBackURL is empty, Signority will not push the document back to your server
Notify Method : POST <Signority sends two requests to your server, one is to push the document in JSON to your server, another is to push the signed files back to your server. If it doesn’t meet your requirement, please contact us.>
You can set a different URL for each document.

Constants

Term	Definition
Base URL	Defined to be: https://sign.signority.com/api
Document	A set of files that need to be signed. A document is like an envelope
Files	A document contains one or more files, of which can be signed by a signing party
Tags	Tags locate on the specific page at a specific location. Tags are fields for the signers to fill in or sign
docID	The ID of a document, can be viewed either through a request or by looking at the URL of the document
fileID	The ID of a file, can be viewed either through a request