Sertifi API Web Service
| Method | /testsite/Services/Gateway.asmx/ApplySignature |
| Method | /testsite/Services/Gateway.asmx/ApplySignature |
| Sertifi API Web Service > All Operations Resource Group : /testsite/Services/Gateway.asmx/ApplySignature (Method) |
Use this call to sign a document.
Requires the domain of the email address to match the site, so only members of the owning organization can be signed for automatically.
Only sign documents when it becomes that signer's turn to sign.
The request body is of type ApplySignature.
| Name | Description | Data Type |
|---|---|---|
| pstr_APICode | The API code of the site. This can be found through your Sertifi web interface under Administration -> Account Settings. | xml:string |
| pstr_FileID | The id of the relevant file. | xml:string |
| pstr_DocumentID | The id of the relevant document. | xml:string |
| pstr_NameSigned | Name to sign with. | xml:string |
| pstr_Email | Email of the user you wish to sign with. | xml:string |
| pstr_CustomField1 | Information to put in first custom field. | xml:string |
| pstr_CustomField2 | Information to put in second custom field. | xml:string |
| pstr_CustomField3 | Information to put in third custom field. | xml:string |
| pstr_CustomField4 | Information to put in fourth custom field. | xml:string |
The response body is of type ApplySignatureResponse.
| Name | Description | Data Type |
|---|---|---|
| ApplySignatureResult | "SUCCESS" or error message. | xml:string |
There's a known bug where you can apply a signature out of order. Using that bug will result in this call breaking your work-flow unexpectedly when it gets fixed.
Common Errors include:
"ERROR: Invalid API Code"
"ERROR: Invalid signature name"
"ERROR: Invalid signer email"
"ERROR: Invalid signer email: ..."
"ERROR: Invalid domin for ApplySignature"
"ERROR: File could not be accessed"
"ERROR: Document could not be accessed"
"ERROR: Document Expired"
"ERROR: Could not load form with Prefill data"
"ERROR: Custom field 1 is invalid, please enter ..."
"ERROR: Custom field 2 is invalid, please enter ..."
"ERROR: Custom field 3 is invalid, please enter ..." (currently contains a typo that says a 1 instead of 3)
"ERROR: Custom field 4 is invalid, please enter ..." (currently contains a typo that says a 1 instead of 4)
"ERROR: Specified email is not a signer for this transaction"
"ERROR: Specified signer signed this document already."